Enrich up to 50 companies in one request. Each item takes the same identifiers as Companies Enrich and is matched independently (id, then linkedin_id, linkedin_url, domain, name); the response buckets items into matched, not_matched and invalid, echoing each item's identifier so you can correlate results. Free: spends no credits; 1 unit of the enrich rate limit per item, none for companies your workspace saved. Authenticate with your API key in the x-api-key header.

How are credits spent?

Company Bulk Enrich is free - matching and returning company profiles never charges credits.

How the batch behaves

Each of the up to 50 items is looked up independently with the same identifier precedence as Company Enrich - id, then linkedin_id, linkedin_url, domain, then name. One item failing never fails the batch: the response splits items into three buckets, each entry echoing your identifier (or the item's index if you did not send one):

• matched - the company was found; carries matched_by and the full Company object.
• not_matched - the identifiers were valid but no company matched; carries the attempted lookup fields.
• invalid - the item could not be looked up at all; carries a reason.

Prefer this endpoint over looping single Company Enrich calls: 50 lookups in one request instead of 50 round trips, with per-item outcomes you can correlate by identifier.

Body parameters

• dataobject[]required

  Array of company lookup items (1-50). Each item is matched independently using priority order id > linkedin_id > linkedin_url > domain > name.

  Field	Type	Description
  identifier	string	Client-supplied correlation key echoed back in the response. If omitted, the item index is used.
  id	string	The GetProspect company id, as returned by Company Search and in People Search results.
  linkedin_id	one of	The LinkedIn company ID (numeric, string or number).
  linkedin_url	string	The LinkedIn company URL.
  domain	string	The company domain.
  name	string	The company name.

Responses

• 200 Every item in exactly one bucket, with the bucket counts in metadata. Two items with one identifier but different lookup keys answer 400 instead.
• 400 Invalid request (VALIDATION_ERROR; payload.code says which kind of mistake).
• 401 Missing, unknown or inactive credentials (UNAUTHORIZED).
• 429 Over the enrich rate limit (RATE_LIMIT); wait Retry-After seconds. Sent only where rate limits are enforced.
• 500 Unexpected server error.

For error handling see Errors. Response objects are described in Person object and Company object.