Skip to main content
This page collects identifier recipes for Company Enrich. Each example is a full working request you can copy, paste, and adapt. For the core walkthrough (first enrichment by domain, response shape), see Company Enrich. For the full list of request and response fields, see Enrich reference.
Replace YOUR_API_KEY in each example with your actual API key. All requests require the x-api-version: 2025-11-01 header.

​
Enrich by profile URL

If you have a company profile URL, pass it in professional_network_profile_urls. This gives you a direct match. 
curl --request POST \
  --url https://api.crustdata.com/company/enrich \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "professional_network_profile_urls": [
      "https://www.linkedin.com/company/serverobotics"
    ]
  }'
Response trimmed for clarity.
Profile URL lookups are direct matches — they typically return a single match with high confidence.

​
Enrich by company name

You can also enrich by company name. This is useful when you only have a name from a form submission or event badge scan. 
curl --request POST \
  --url https://api.crustdata.com/company/enrich \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "names": ["Retool"]
  }'
Name-based enrichment may return multiple candidates. Check confidence_score and primary_domain to pick the right match.

​
Enrich by company ID

If you already have a Crustdata company ID (from a previous search call), pass it in crustdata_company_ids for an exact lookup. 
curl --request POST \
  --url https://api.crustdata.com/company/enrich \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "crustdata_company_ids": [633593]
  }'
Company ID lookups typically return a single exact match, making this the most precise enrichment method.

​
Use exact match for stricter domain matching

By default, domain-based enrichment can return multiple candidates. Set exact_match: true to restrict results to companies whose primary_domain exactly matches your input. 
curl --request POST \
  --url https://api.crustdata.com/company/enrich \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "domains": ["cashfree.com"],
    "exact_match": true
  }'
Response trimmed for clarity.
With exact_match: true, results are limited to records whose primary_domain exactly matches your input. You may still receive multiple matches when more than one company record shares that same domain.

​
Enrich multiple companies in one request

The same endpoint supports multiple identifiers in a single request, so multi-company enrich stays on this page rather than as a separate API. 
curl --request POST \
  --url https://api.crustdata.com/company/enrich \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "crustdata_company_ids": [633593, 628895]
  }'

​
Multi-company enrich tips

  • Submit one identifier type per request. Mixing identifier types (e.g., sending both domains and names) is not supported.
  • Each entry in the response corresponds to the input at the same position, so you can match results back to your input list by index.
  • If some identifiers fail to match, their matches array will be empty, but the request still succeeds for the others.

​
Choosing the right identifier

Each identifier type has trade-offs in precision and convenience.
DomainProfile URLCompany NameCompany ID
PrecisionHighHighestMediumHighest
Best forCRM cleanup, inbound leadsKnown company profilesFuzzy matchingInternal pipelines and search follow-up
Typical matchesOne or more exact-domain candidates1Multiple candidates1

​
Common workflow: Search then Enrich

The most powerful pattern combines Company Search with Company Enrich. Search finds companies matching your criteria; Enrich gets the full profile for each match. Step 1: Search for well-funded software companies. 
curl --request POST \
  --url https://api.crustdata.com/company/search \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "filters": {
      "op": "and",
      "conditions": [
        {
          "field": "basic_info.industries",
          "type": "in",
          "value": ["Software Development"]
        },
        {
          "field": "funding.total_investment_usd",
          "type": ">",
          "value": 10000000
        }
      ]
    },
    "limit": 5,
    "fields": ["crustdata_company_id", "basic_info.name", "basic_info.primary_domain"]
  }'
Step 2: Take the crustdata_company_id values from the search results and pass them in crustdata_company_ids to enrich. 
curl --request POST \
  --url https://api.crustdata.com/company/enrich \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "crustdata_company_ids": [633593, 628895]
  }'
This two-step pattern is the foundation for sales, research, and investment workflows. Search narrows the universe; Enrich fills in the details. Because crustdata_company_ids is an array, the same endpoint works for one company or many companies.

​
Next steps

  • Reference — request parameters, valid fields values, company_data sections, validation, and errors.
  • Enrich reference — request parameters, response fields, validation, errors.
  • Company Autocomplete — discover exact values before building search filters.