Attach Alias

Attach a reviewed alias or record a conflict proposal; never silently merge.

POST/api/v1/leads/dispatch

Request

curl -X POST "<BASE_URL>/api/v1/leads/dispatch" \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "X-CQRS-Action: ATTACH_ALIAS" \
  -H "Content-Type: application/json" \
  -d '{
    "confidence": 12.5,
    "expected_version": 1,
    "kind": "EMAIL",
    "lead_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
    "source": "string",
    "tenant_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
    "value": "string"
  }'

Authorization

Minimum role: Tenant administratorThe caller must hold this role or a higher one.
Action: ATTACH_ALIAS

Headers

AuthorizationstringRequired
Access token of the signed-in user, as a Bearer token. It identifies the user, their role and the workspace.
X-CQRS-ActionstringRequired
Names the command to run. Must be ATTACH_ALIAS for this endpoint.
Content-TypestringRequired
Always application/json.
X-Idempotency-KeystringOptional
A key you choose that is unique to this attempt. A command repeated with the same key is not applied a second time.
X-Correlation-IdstringOptional
Your own identifier for the request. Returned in the x-correlation-id response header; generated when you leave it out.

Request body

confidencenumberRequired
No description yet.
expected_versionintegerRequired
No description yet.
kindenumRequired
Vocabulary of identifier types we recognise on a lead. Adding a new kind here is a deliberate workspace-level decision — every matcher, dedup heuristic, and UI render branch must learn the new variant.
Allowed values
- EMAIL
- PHONE
- LINKEDIN_URL
- TWITTER_HANDLE
- DOMAIN_EMAIL
- EMPLOYEE_BADGE
- O_AUTH_SUBJECT
DOMAIN_EMAIL
Email at a company domain — separated from generic Email so we can boost confidence on company-domain matches.
EMPLOYEE_BADGE
Employer-issued badge / SSO sub identifier.
O_AUTH_SUBJECT
OAuth subject claim — stable across vendor logins.
lead_iduuidRequired
No description yet.
sourcestringRequired
No description yet.
tenant_iduuidRequired
No description yet.
valuestringRequired
No description yet.
source_connector_iduuid or nullOptional
No 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.

successbooleanRequired
true when the command was applied.
error_messagestringRequired
Empty when the command was applied.
projected_stateobjectOptional
The record as it stands after the command.
event_payloadobjectOptional
The event the command recorded.
insightsarray of objectOptional
Advisory notes about the result. Each has a code, a message and an impact number.

Errors

Every error carries an HTTP status. Where it also carries a code, branch on the code, not on the message.

400X-CQRS-Action is missing or names a command this route does not accept. Send ATTACH_ALIAS.
400DOMAIN_ROUTINGThe body is not a valid command. Check the required fields and their types.
401The access token is missing, expired or not valid.
401L1_AUTHThe caller's role is below tenantadmin or the caller has no access to this record.
403L1_POLICYA business rule refused the command. The message names the rule.
409L1_VERSIONexpected_version is not the record's current version. Read the record again, then retry.
409L1_IDEMPOTENCYA command with this idempotency key was already applied.
409CONFLICTThe command would duplicate a record that must be unique.
500L3_COMMITThe command was valid but could not be saved.