Add leads to a lead list in bulk
Accepts up to 100 leads in one request and processes them in the background. All or nothing: if any lead fails validation, the whole batch is refused and nothing is queued.
Every lead is checked first against the same field rules as the single-lead endpoint
(required and well-formed linkedin_profile_url, field lengths, email and phone format,
ISO country code, and so on). If any lead fails, or the batch has more than 100 leads,
the whole request is refused with 422 Unprocessable Entity and nothing is queued. The
error message names each invalid lead by its index in the leads array.
Two leads in one batch with the same LinkedIn URL, once normalised, are refused too.
On success the response is 202 Accepted and the leads are not yet in the lead list.
accepted is the number of leads that passed these checks, not the number that will
end up in the lead list. Shortly after, each lead is created if it does not exist (matched
by linkedin_profile_url) or updated if it does, then added to the lead list. A lead the
workspace cannot store (for example an email already used by another lead, which the
single-lead endpoint would report as 422) is skipped and logged. A lead that is
already in the list is skipped, exactly as the bulk action in the app behaves. The response does
not report which leads were skipped; list the lead list’s leads to see the result.
Works with a workspace API key or an agency API key for a linked workspace. Adding leads does not use enrichment credits.
Path Parameters
Body
Response
Batch accepted and queued. The leads are added shortly after.

