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

​
Identify by company name

Name-based identification often returns multiple candidates. Check confidence_score and primary_domain to pick the right match. 
curl --request POST \
  --url https://api.crustdata.com/company/identify \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "names": ["Serve Robotics"]
  }'
When multiple matches are returned, use primary_domain and employee_count_range to disambiguate. The first match is not always the right one for name-based lookups.

​
Identify by profile URL

If you have a company profile URL, pass it in professional_network_profile_urls. Profile URL lookups are direct matches — they typically return a single match with high confidence. 
curl --request POST \
  --url https://api.crustdata.com/company/identify \
  --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/mintlify"
    ]
  }'

​
Identify by Crustdata company ID

Pass a Crustdata company ID (for example, from a previous search call) to crustdata_company_ids for an exact lookup. 
curl --request POST \
  --url https://api.crustdata.com/company/identify \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "crustdata_company_ids": [628895]
  }'
Company ID lookups return an exact match.

​
Common workflow: Inbound domain → Identify → Search for similar companies

An inbound lead arrives from a known domain. Use Identify to resolve the domain to a company record, then use Search to find similar companies for prospecting.

​
Step 1: Identify the inbound company

curl --request POST \
  --url https://api.crustdata.com/company/identify \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{"domains": ["retool.com"]}'
Extract: Take response[0].matches[0].company_data.basic_info.industries[0] → "Software Development" and employee_count_range → "201-500".

​
Step 2: Search for similar 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": "headcount.total", "type": ">", "value": 200},
        {"field": "headcount.total", "type": "<", "value": 1000}
      ]
    },
    "sorts": [{"column": "headcount.total", "order": "desc"}],
    "limit": 10,
    "fields": ["crustdata_company_id", "basic_info.name", "basic_info.primary_domain", "headcount.total"]
  }'
Extract: Take companies[].crustdata_company_id values and pass them to Enrich for full profiles of promising matches. If empty: If companies is [], broaden your filters (for example, wider headcount range or more industries). Use Autocomplete to verify valid filter values.

​
Next steps

  • Identify reference — request parameters, validation, errors, API summary.
  • Company Enrich — pass the crustdata_company_id from Identify into Enrich to get the full profile.
  • Company Search — find similar companies by industry, headcount, or funding.