DealSleek API · Leads
PreviewRecord Lead Consent
Record a lawful basis for contacting a lead on one or more channels, with an evidence pointer. Append-only; the write side of the consent ledger every outbound action already reads.
/api/v1/leads/dispatchHeaders
AuthorizationstringRequiredAccess token of the signed-in user, as a Bearer token. It identifies the user, their role and the workspace.
X-CQRS-ActionstringRequiredNames the command to run. Must be
RECORD_LEAD_CONSENTfor this endpoint.Content-TypestringRequiredAlways
application/json.X-Idempotency-KeystringOptionalA key you choose that is unique to this attempt. A command repeated with the same key is not applied a second time.
X-Correlation-IdstringOptionalYour own identifier for the request. Returned in the
x-correlation-idresponse header; generated when you leave it out.
Request body
channelsarray of enumRequiredOne grant is written per channel. Empty is refused — a consent record that permits nothing is an audit trail with no subject.
- Allowed values
- SMS
- PHONE
- PROGRAMMATIC_AD
- AI_OUTREACH
- POSTAL
- minimum items 1
evidence_refstringRequiredPointer to the evidence: form submission id, list vendor + contract ref, signed agreement, recorded opt-in. Required, and deliberately not defaulted — "we have consent" without a pointer is an assertion, not a record, and it is the thing a regulator asks to see.
- minimum length 1
jurisdictionobjectRequiredNo description yet.
2 child fields
countrystringRequiredISO 3166-1 alpha-2 (
"US","DE","BD").subRegionstringRequiredSub-region for split regimes (
"US-CA","DE-BY"). Empty = whole country.
lead_iduuidRequiredNo description yet.
expires_atdate-time or nullOptionalNone= open-ended. Jurisdictions with a fixed consent lifetime should set this so the grant self-expires rather than relying on a cleanup job.
Response
Status 202. The command was applied. The body reports the outcome and, where the command changes a record, that record's new state.
successbooleanRequiredtruewhen the command was applied.error_messagestringRequiredEmpty when the command was applied.
projected_stateobjectOptionalThe record as it stands after the command.
event_payloadobjectOptionalThe event the command recorded.
insightsarray of objectOptionalAdvisory notes about the result. Each has a
code, amessageand animpactnumber.
Errors
Every error carries an HTTP status. Where it also carries a code, branch on the code, not on the message.
- 400
X-CQRS-Actionis missing or names a command this route does not accept. SendRECORD_LEAD_CONSENT. - 400
DOMAIN_ROUTINGThe body is not a valid command. Check the required fields and their types. - 401The access token is missing, expired or not valid.
- 401
L1_AUTHThe caller's role is belowrepor the caller has no access to this record. - 403
L1_POLICYA business rule refused the command. The message names the rule. - 409
L1_IDEMPOTENCYA command with this idempotency key was already applied. - 409
CONFLICTThe command would duplicate a record that must be unique. - 500
L3_COMMITThe command was valid but could not be saved.