Skip to main content
POST
Bulk Enrich Contacts
Queues email and/or mobile phone enrichment for many (company, contact) pairs at once. Returns one result per requested pair, in request order — poll each result’s enrichmentId via Enrichment Status. A bad or unaffordable pair degrades to a per-item message instead of failing the whole batch.
Enriching costs credits - see the Credit usage section

Request

Accept-Language
string
default:"EN"
  • NL: Dutch - FR: French - EN: English

Body

companyContacts
array
You can request up to 100 companies at once.
enrichEmail
boolean
default:"false"
Enrich contacts with an email address, if available.
enrichMobilePhone
boolean
default:"false"
Enrich contacts with a mobile phone number, if available.
At least one of enrichEmail or enrichMobilePhone must be true.

Response

Returns 202 Accepted. Unlike the single endpoint, no Location header is set (there’s no single created resource to point at).
When any pair in the batch is charged, the response includes X-Bizzy-Credits-Balance and X-Bizzy-Credits-Charged headers — the balance reflects the post-charge total, and the charged amount is summed across all charged pairs in the batch. See Credit usage.
results
array
One entry per requested (company, contact) pair, in request order.
enrichmentId
string | null
Obfuscated id used to poll the Enrichment Status endpoint. null when message is set.
status
string | null
Always PENDING on creation, or null when message is set.
message
string | null
Set when this pair could not be queued (e.g. contact not found), leaving enrichmentId/status null. Other pairs in the batch are unaffected.