Record Discovery

Persist a newly-found email + person record from a discovery source.

POST/api/v1/finder/dispatch

Request

curl -X POST "<BASE_URL>/api/v1/finder/dispatch" \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "X-CQRS-Action: RECORD_DISCOVERY" \
  -H "Content-Type: application/json" \
  -d '{
    "confidence": 0,
    "domain": "string",
    "email": "jordan.lee@example.com",
    "source": "WEB",
    "tenant_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }'

Authorization

Minimum role: Sales repThe caller must hold this role or a higher one.
Action: RECORD_DISCOVERY

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 RECORD_DISCOVERY 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.
at least 0
at most 1
domainstringRequired
No description yet.
minimum length 1
emailstringRequired
No description yet.
minimum length 3
sourceenumRequired
Where a discovery came from. Drives confidence weighting and the "Add lead" promote flow (LinkedIn evidence > a permutation guess).
Allowed values
- WEB
- LINKEDIN
- MCP
- MX
- GITHUB
- MANUAL_ENTRY
- TRIANGULATED
- PERMUTATION
tenant_iduuidRequired
No description yet.
departmentstring or nullOptional
No description yet.
first_namestring or nullOptional
No description yet.
last_namestring or nullOptional
No description yet.
linkedin_urlstring or nullOptional
No description yet.
messagestring or nullOptional
Optional probe reason persisted alongside the status.
positionstring or nullOptional
No description yet.
verification_statusenum or nullOptional
Outcome of an SMTP RCPT-TO probe (or its fallback path).
Allowed values
- UNKNOWN
- VALID
- INVALID
- CATCH_ALL
- DISPOSABLE
- RISKY
- PROBABLE

Response

Status 202. The command was applied. The body is the record as it stands after the command: a JSON object whose fields depend on the record.

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 RECORD_DISCOVERY.
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 rep or the caller has no access to this record.
403L1_POLICYA business rule refused the command. The message names the rule.
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.