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
leadsrequiredarray<object>
1-1,000 person records.
lead_source· optionalstring
Source label; default crm, max 120 characters.
resolve_name_only_companies· optionalboolean
Resolve company identity from names when domain is absent; default true.
provider· optionalstring
Optional provider identifier.
connection_id· optionalstring
Optional provider connection ID.
remote_object_type· optionalstring
Remote object type; default person.
ownerUserId· optionalstring
Lead owner user ID.
| Name | Type | Description |
|---|---|---|
| leadsrequired | array<object> | 1-1,000 person records. |
| lead_source | string | Source label; default crm, max 120 characters. |
| resolve_name_only_companies | boolean | Resolve company identity from names when domain is absent; default true. |
| provider | string | Optional provider identifier. |
| connection_id | string | Optional provider connection ID. |
| remote_object_type | string | Remote object type; default person. |
| ownerUserId | string | Lead owner user ID. |
Errors
| Status | Meaning |
|---|---|
| 400 | Invalid batch or a lead has no person identity signal. |
| 401 | Missing or invalid user session. |
| 403 | Developer API keys are not supported on this route. |
