Skip to main content

Bulk delete leads

Queue deletion for selected leads after active outreach cleanup.

POST/api/leads/delete
HTTP referenceScope leads:writeUpdated April 25, 2026

This page documents the canonical HTTP contract for this endpoint.

This returns a queue receipt. Poll the operation run with operation_run_id (requires jobs:read) to confirm completion. The authenticated organization determines the selection scope. Explicit IDs are trimmed and deduplicated, then capped at 5,000 after any selection limit; inaccessible or missing explicit IDs are rejected. Descriptor selections are resolved by the background job, so initial requested/matched counts can be null. Pending outreach is stopped before records are removed; enrollment, task and delivery audit history is retained.

Body parameters

  • lead_ids · optional

    array<string>

    Explicit lead IDs to delete. Provide either lead_ids or selection.

  • selection · optional

    object

    Bulk selection object with mode (ids or descriptor), descriptor filter, search, scope, etc.

  • scope · optional

    string

    Lead scope: org or user.

  • source_table_id · optional

    string

    Research table context for descriptor selection.

  • source_table_scope · optional

    string

    Research scope: company or lead.

Errors

StatusMeaning
400Invalid payload or some leads not found.
401Invalid API key or missing auth.
403Missing leads:write scope.
404No leads found for selection.

Docs