DealSleek API · Leads
PreviewMap Intake Fields
Bind JSON payload paths to lead fields for an automated intake binding. The path-shaped twin of MAP_IMPORT_COLUMNS; both write the batch's column_map.
/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
MAP_INTAKE_FIELDSfor 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
batch_iduuidRequiredNo description yet.
current_statusenumRequiredBatch lifecycle. Nothing is written to
leadsbefore COMMITTING, so an operator can upload, map and validate without consequence — the dry run is the whole reason the aggregate exists.- Allowed values
- UPLOADED
- MAPPED
- VALIDATED
- COMMITTING
- COMPLETED
- REJECTED
- CANCELLED
- ROLLED_BACK
- PARTIAL
- PARTIAL
- Committed, but some rows failed. Distinct from Completed because the operator has a reject list to act on.
email_pathstringRequiredRequired, for the same reason the CSV mapping requires it: a record with no address cannot become a lead, cannot be deduped, and cannot be contacted. Refused up front rather than validated into an INVALID row.
- minimum length 1
company_pathstring or nullOptionalNo description yet.
consent_evidence_pathstring or nullOptionalWhere the lawful basis lives in the payload — a platform's consent text id, a form's checkbox, our own submission id. Absent means this binding carries no evidence and its records quarantine as CONSENT_MISSING.
first_name_pathstring or nullOptionalNo description yet.
last_name_pathstring or nullOptionalNo description yet.
phone_pathstring or nullOptionalNo description yet.
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. SendMAP_INTAKE_FIELDS. - 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 belowmanageror 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.