Job Batch Search - Crustdata Docs

Batch job search runs one asynchronous job and delivers the entire result set as a single file. Where Search Jobs returns one cursor page per call, a batch job walks every page for you and returns all listings for the companies you name.

Batch search

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

Retrieve every job listing in the dataset for up to 10 companies in a single asynchronous job. Records in the downloaded file are flat, identical to the non-batch Search Jobs record shape.

How batch job search differs from non-batch search

Companies, not filters. Provide a crustdata_company_ids list — a JSON array of integers (a comma-separated string is rejected). The job returns all listings for those companies. To search listings by arbitrary filters, use the non-batch Search Jobs instead.
Up to 10 companies per job. More than 10 IDs returns 400. Resolve IDs from a name, domain, or profile URL with the free Company Identify endpoint.
Whole result set. The job paginates server-side and delivers every listing — there is no max_results or cursor control.
Flat records. Each line in the results file has exactly the non-batch Search Jobs record shape. No envelope.
Exact field projection. When you pass fields, each record contains exactly those dotted paths — nothing more. Omit fields to get every field your account can read. The selectable fields are the same as non-batch Search Jobs.

curl --request POST \
  --url https://api.crustdata.com/batch/job/search \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "crustdata_company_ids": [6036032]
  }'

{
    "batch_id": "0afed646-ce96-430a-92c0-b6b7589e937c",
    "status": "pending",
    "entity": "job",
    "action": "search",
    "identifier_count": 1,
    "entities_requested": 1,
    "status_url": "/batch/0afed646-ce96-430a-92c0-b6b7589e937c"
}

The response is a ticket, not the listings — status: "pending" means the job is queued. Poll it with GET /batch/{batch_id} until status reaches completed, then download the results file, as described in Working with batch jobs below. (Search jobs always report identifier_count: 1 — the one submission.) To keep each record small, project just the fields you need:

Request body — and URL only

{
    "crustdata_company_ids": [6036032],
    "fields": ["job_details.title", "job_details.url"]
}

When the job completes, the downloaded file has one flat JSON record per line — exactly the fields you requested:

The results file (title and URL only)

{"job_details": {"title": "Senior Software Engineer", "url": "https://example.com/careers/senior-software-engineer"}}
{"job_details": {"title": "Product Manager, Growth", "url": "https://example.com/careers/product-manager-growth"}}

Errors

400 — no company IDs

{
    "error": {
        "type": "invalid_request",
        "message": "Exactly one identifier must be provided: crustdata_company_ids",
        "metadata": []
    }
}

400 — comma-separated string instead of a JSON array

{
    "error": {
        "type": "invalid_request",
        "message": "crustdata_company_ids must be a list",
        "metadata": []
    }
}

400 — more than 10 company IDs

{
    "error": {
        "type": "invalid_request",
        "message": "Maximum 10 identifiers allowed for job/search. Found 11",
        "metadata": []
    }
}

What to do next

Build queries interactively first — iterate with Search Jobs page by page, then pull the full set for your target companies as a batch job.
Look up fields — see the Search reference.
Resolve company IDs — use the free Company Identify endpoint.
Search people or companies in batch — see Batch Person Search or Batch Company Search.
Full schema — see the API reference.

​Batch search

​How batch job search differs from non-batch search

​Errors

​What to do next

Batch search

How batch job search differs from non-batch search

Errors

What to do next