Company Batch Search

• Batch search — results served from the indexed database, higher caps and faster (up to 10,000 records).
• Batch live search — results retrieved from the web in real time, fresher but capped lower (up to 1,000 records).

​

Batch search

POST https://api.crustdata.com/batch/company/search

​

How batch search differs from non-batch search

• One query, whole result set. You submit a single query; the job paginates server-side until max_results is reached or the matches run out.
• max_results is the only volume control. It clamps to 10,000 and defaults to that cap when omitted. Values above the cap are silently clamped; zero or negative values return 400. The non-batch paging knobs — limit, page, preview — are silently ignored.
• Flat records. Each line in the results file has exactly the non-batch search record shape. No envelope.
• Exact field projection. When you pass fields, each record contains exactly those fields — nothing more. Omit fields to get every field your account can read.

​

Database batch search

curl --request POST \
  --url https://api.crustdata.com/batch/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": "headcount.total", "type": ">", "value": 1000}
      ]
    },
    "max_results": 2,
    "fields": ["basic_info.name", "basic_info.primary_domain", "headcount.total"]
  }'

{
    "batch_id": "ee438e6f-7449-481f-9a2d-2ef57ddab24a",
    "status": "pending",
    "entity": "company",
    "action": "search",
    "identifier_count": 1,
    "entities_requested": 1,
    "status_url": "/batch/ee438e6f-7449-481f-9a2d-2ef57ddab24a"
}

{"basic_info": {"name": "Aarti Industries Ltd.", "primary_domain": "aarti-industries.com"}, "headcount": {"total": 4923}}
{"basic_info": {"name": "Aditya Birla Capital", "primary_domain": "adityabirlacapital.com"}, "headcount": {"total": 31747}}

​

Two warnings before you submit large jobs

​

Errors

{
    "error": {
        "type": "invalid_request",
        "message": "`filters` must be provided for search",
        "metadata": []
    }
}

{
    "error": {
        "type": "invalid_request",
        "message": "`max_results` must be a positive integer",
        "metadata": []
    }
}

​

Batch live search

POST https://api.crustdata.com/batch/company/professional_network/search/live

​

How batch live search differs from non-batch search

• One query, whole result set. You submit a single query; the job paginates server-side until max_results is reached or the matches run out.
• max_results is the only volume control. It clamps to 1,000 and defaults to that cap when omitted. Values above the cap are silently clamped; zero or negative values return 400. The non-batch paging knobs — limit, page, preview — are silently ignored.
• Flat records. Each line in the results file has exactly the non-batch search record shape. No envelope.
• Exact field projection. When you pass fields, each record contains exactly those fields — nothing more. Omit fields to get every field your account can read.

​

Live batch search

curl --request POST \
  --url https://api.crustdata.com/batch/company/professional_network/search/live \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "filters": [
      {"field": "COMPANY_HEADCOUNT", "type": "in", "value": ["11-50"]},
      {"field": "REGION", "type": "in", "value": ["United States"]}
    ],
    "max_results": 2,
    "fields": ["basic_info.name", "headcount.total"]
  }'

{
    "batch_id": "eeba5683-b309-40a8-862d-b89e7ca78276",
    "status": "pending",
    "entity": "company",
    "action": "search_live",
    "identifier_count": 1,
    "entities_requested": 1,
    "status_url": "/batch/eeba5683-b309-40a8-862d-b89e7ca78276"
}

{"basic_info": {"name": "Annie Rose Inc"}, "headcount": {"total": 31}}
{"basic_info": {"name": "Stanford Law Review"}, "headcount": {"total": 18}}

{"field": "ANNUAL_REVENUE", "type": "between", "value": {"min": 1, "max": 500}, "sub_filter": "USD"}

{
    "professional_network_search_url": "https://www.linkedin.com/sales/search/company?query=...",
    "max_results": 100
}

​

Errors

{
    "error": {
        "type": "invalid_request",
        "message": "Either `filters` or `professional_network_search_url` must be provided for live search",
        "metadata": []
    }
}

{
    "error": {
        "type": "invalid_request",
        "message": "`max_results` must be a positive integer",
        "metadata": []
    }
}

​

What to do next

• Build queries interactively first — iterate with Company Search or Company Live Search page by page, then submit the final query as a batch job.
• Look up operators and fields — see the search reference.
• Enrich the companies you found — see Batch Company Enrich.
• Search people in batch — see Batch Person Search.
• Search jobs in batch — see Batch Job Search.
• Full schema — see the API reference.