Skip to main content

Create leads in bulk

Create or resolve up to 1,000 Lead records in one request.

POST/api/leads/bulk
HTTP referenceScope User session required; developer API keys unsupportedUpdated September 27, 2026

This page documents the canonical HTTP contract for this endpoint.

Requires an authenticated user session. The current HTTP scope resolver rejects developer API keys, even though the operation catalog declares command scopes.

Each lead needs at least one person identity signal such as a name, email, phone, or LinkedIn identifier. Maximum batch size is 1,000. The actual result reflects identity resolution and duplicate handling.

Body parameters

  • leadsrequired

    array<object>

    1-1,000 person records.

  • lead_source · optional

    string

    Source label; default crm, max 120 characters.

  • resolve_name_only_companies · optional

    boolean

    Resolve company identity from names when domain is absent; default true.

  • provider · optional

    string

    Optional provider identifier.

  • connection_id · optional

    string

    Optional provider connection ID.

  • remote_object_type · optional

    string

    Remote object type; default person.

  • ownerUserId · optional

    string

    Lead owner user ID.

Errors

StatusMeaning
400Invalid batch or a lead has no person identity signal.
401Missing or invalid user session.
403Developer API keys are not supported on this route.

Docs