Skip to main content

Bulk update a lead field

Set or clear one writable catalog field across an explicit lead selection. Standard-field and custom-field updates are queued; poll the returned operation_run_id for completion.

POST/api/leads/bulk_field_update
HTTP referenceScope leads:writeUpdated September 27, 2026

This page documents the canonical HTTP contract for this endpoint.

Developer API keys need the listed scope. A valid authenticated user session may also call this route.

For standard fields, the queued result is admission, not completion. Poll GET /api/operation-runs/{operation_run_id}. Custom-field updates use the existing user-admin custom-field writer and are also queued; poll the returned operation_run_id until terminal state. Choose an editable field and field_ref from the CRM field catalog.

Body parameters

  • selection · optional

    object

    Lead selection; mutually exclusive with lead_ids.

  • lead_ids · optional

    array<string>

    Legacy explicit lead IDs; mutually exclusive with selection.

  • field_refrequired

    string

    CRM catalog ID for a writable Lead field.

  • operationrequired

    string

    set or clear.

  • value · optional

    any

    Required and non-null for set; omit or send null for clear.

  • provenance · optional

    object

    Optional qualification provenance for eligible custom-field conclusions; not accepted for clear or standard fields.

Errors

StatusMeaning
401Authentication is missing or invalid.
403The credential is invalid or lacks the required scope.
400Selection or field lookup failed.
422Operation must be set or clear; set requires a non-null, non-empty value; clear may omit value or send null; non-null values are rejected; selection and lead_ids are mutually exclusive.
404No leads match the selection.
409The catalog field has no supported bulk writer.

Docs