Replace
YOUR_API_KEY in each example with your actual API key. All
requests require the x-api-version: 2025-11-01 header.Request body
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
domains / professional_network_profile_urls / names / crustdata_company_ids | array | Yes — one only | — | Submit exactly one identifier type. |
fields | string[] | No | ["basic_info"] | Sections of company_data to include in the response. |
exact_match | boolean | No | null | Set to true to restrict results to exact primary_domain matches. |
Response body
The response is a top-level array. Each entry corresponds to one input identifier.| Field | Type | Description |
|---|---|---|
matched_on | string | The input identifier you submitted |
match_type | string | domain, name, crustdata_company_id, professional_network_profile_url |
matches | array | Candidate matches. Empty for no-match inputs. |
matches[].confidence_score | number | Higher is better. 1.0 is common for direct identifier lookups. |
matches[].company_data | object | Full enriched company profile. |
Rate limits and pricing
Current platform behavior — not specified in the OpenAPI contract:
Pricing:
2 credits per record.- Rate limit: 15 requests per minute.
If you only need lightweight discovery, start with
Company Search, then enrich the companies you want
in full detail.
Identifiers
Enrich by profile URL, name, or company ID. Exact match and
multi-company requests.
Reference
Request parameters, response fields, valid
fields values,
company_data sections, validation, errors.Your first enrichment: look up a company by domain
The simplest enrichment takes a website domain and returns matching company profiles. Pass the domain in thedomains array.
description in basic_info is truncated in this snippet for readability.
Other fields reflect the default response — when fields is omitted,
company_data only contains crustdata_company_id and basic_info.
Request additional sections such as headcount, funding, or people
explicitly via fields (see
Using the fields parameter).Understanding the response
The Enrich API returns a top-level array — one entry per identifier you submitted. Each entry has three fields:matched_on— the identifier you submitted (the domain, URL, name, or ID).match_type— which identifier type was used. Possible values:domain,name,crustdata_company_id,professional_network_profile_url.matches— an array of candidate companies. Each match includes aconfidence_scoreand the fullcompany_dataobject.
confidence_score indicates the best match. Use exact_match: true
to restrict results to companies whose primary_domain exactly matches your
input (see
Identifiers).
How to interpret results
- Multiple matches: If
matchescontains more than one entry, checkconfidence_score— the highest score is the best match. Useprimary_domainto verify. - Empty
matchesarray: The identifier did not match any company. Check for typos or try a different identifier type. confidence_score: Higher is better. A score of1.0is common for direct identifier lookups such as profile URLs or company IDs.
What to do next
- Enrich by other identifiers — see Identifiers for profile URL, name, company ID, exact match, and multi-company requests.
- Look up request/response details and
fields— see Enrich reference for request parameters,company_datasections, and validfieldsvalues. - Search for companies first — use Company Search to find companies by industry, funding, headcount, and more, then enrich the matches.
- Discover filter values — use Autocomplete to find valid values before building search filters.

