Create or update leads in bulk
Accepts up to 100 leads in one request and processes them in the background. The same
batch as the lead list and campaign bulk endpoints, with no destination: each lead is
created if it does not exist (matched by linkedin_profile_url) or updated if it does,
and nothing else happens. No lead list and no campaign membership is written.
All or nothing on validation. 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 nothing has been written yet. accepted
is the number of leads that passed these checks. A lead the workspace cannot store is
skipped and logged, and a lead already on the blacklist is left exactly as it is. The
response does not report which leads were skipped; list the workspace’s leads to see the
result.
Works with a workspace API key or an agency API key for a linked workspace. This spends no enrichment credits.

