DealSleek API · Finder

Preview

Promote To Lead

Convert a verified email discovery into a lead aggregate.

POST/api/v1/finder/dispatch

Authorization

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

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 PROMOTE_TO_LEAD 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

  • discovery_iduuidRequired

    No description yet.

  • lead_iduuidRequired

    Echo the freshly-created lead_id so the discovery row can carry a back-reference (stored in metadata if a column doesn't exist).

  • tenant_iduuidRequired

    No description yet.

  • storedobject or nullOptional

    No description yet.

    7 child fields
    • emailstringRequired

      No description yet.

    • iduuidRequired

      No description yet.

    • 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.

    • verification_statusenumRequired

      Outcome of an SMTP RCPT-TO probe (or its fallback path).

      Allowed values
      • UNKNOWN
      • VALID
      • INVALID
      • CATCH_ALL
      • DISPOSABLE
      • RISKY
      • PROBABLE
    • versionintegerRequired

      No description yet.

    • linkedin_urlstring or nullOptional

      No description yet.

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 PROMOTE_TO_LEAD.
  • 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.
Generated from the API contract · revision dc3fcb53de3f8af7