Create multiple leads in a single request
/api/v1/records/bulk instead of /api/v1/leads/bulk. Both endpoints are functionally identical - use whichever naming convention fits your integration.phoneNumber directly for each lead.externalId only. Phone fetched via predial function before calling.phoneNumber or externalId. You can mix modes within the same bulk request.write scopeexternalId first - if provided, checks for existing lead with same externalId in campaignphoneNumber - if provided, checks for existing lead with same phone in campaign| Error | Cause | Solution |
|---|---|---|
campaignId is required | Missing campaignId | Include campaignId in request body |
leads array is required | Missing or invalid leads | Include leads array in request body |
leads array cannot be empty | Empty leads array | Add at least one lead to the array |
Maximum 1000 leads per bulk request | Too many leads | Split into multiple requests |
leads[N]: At least one of phoneNumber or externalId is required | Lead missing both identifiers | Each lead needs phoneNumber or externalId |
Batch Size
Scheduling
Validation
Error Handling
created vs skipped countsskippedIdentifiers for investigationPrefetch Mode