Skip to main content

Bulk mobile find

Trigger phone number enrichment for selected leads. Skips leads that already have a mobile number.

POST/api/leads/bulk-mobile-find
HTTP referenceScope leads:read + leads:writeUpdated April 25, 2026

This page documents the canonical HTTP contract for this endpoint.

The route also accepts a top-level ID array. Existing mobile numbers and prior not_found results (unless skip_previously_attempted is false) are skipped. Remaining Leads need an email, LinkedIn URL, or first and last name plus company name/domain. This illustrates the queued case; queued responses include job_id, operation_run_id, operationRunId, processable_ids, limit_reached and process_limit. Poll a queued operation with GET /api/operation-runs/{operation_run_id} (requires jobs:read). When no leads qualify it returns success and skipped details without job IDs.

Body parameters

  • lead_ids · optional

    array<string>

    Explicit lead IDs. Provide either lead_ids or selection.

  • selection · optional

    object

    BulkSelectionModel using ids or descriptor mode.

  • scope · optional

    string

    Optional org or user selection scope.

  • source_table_id · optional

    string

    Optional Research Table context.

  • source_table_scope · optional

    string

    Optional company or lead Research Table scope.

  • process_limit · optional

    integer

    Optional maximum to process; integer 1 through 10,000.

  • skip_previously_attempted · optional

    boolean

    Skip leads with prior not_found result. Defaults to true.

Errors

StatusMeaning
400Invalid payload or some leads not found.
401Invalid API key or missing auth.
403Missing leads:read or leads:write scope.
404No leads found for selection.
503Failed to queue mobile finding task.

Docs