---
title: "List batch jobs for the authenticated account"
method: GET
path: "/batch"
tags: ["Batch APIs"]
---

# List batch jobs for the authenticated account

`GET /batch`

List your batch jobs, most recent first, with cursor-based pagination and optional status
filtering. Job summaries carry the same fields as the job-status endpoint minus the download
links — poll `GET /batch/{batch_id}` for a specific job to obtain its `download_url`.



The `x-api-version` header is not required on this endpoint.

## Query parameters

- `limit` integer
- `status` 'pending' | 'processing' | 'completed' | 'failed'
- `cursor` string, uuid

## Response `200`

Paginated list of batch jobs

- BatchJobListResponse — Paginated list of batch jobs for the authenticated account, most recent first.
  - `jobs` BatchJobSummary[], required — Batch jobs on this page.
    - `batch_id` string, uuid, required — Unique ID of the batch job.
    - `status` 'pending' | 'processing' | 'completed' | 'failed', required — Job lifecycle status.
    - `entity` string, required — Entity type the job operates on (`company` or `person`; historical jobs may report legacy entity names).
    - `action` string, required — Internal action name for the job (`enrich`, `enrich_live`, `search`, or `search_live`).
    - `identifier_count` integer, required — Number of identifiers submitted. Search jobs always report `1` (the query).
    - `result_count` integer, required — Number of records the job produced.
    - `entities_requested` integer, required — Number of entities the job was asked to produce.
    - `entities_fulfilled` integer, required — Number of entities actually delivered.
    - `created_at` string, date-time, nullable, required — When the job was submitted (ISO 8601).
    - `completed_at` string, date-time, nullable, required — When the job finished (ISO 8601). `null` while the job is still pending or processing.
    - `error_message` string — Human-readable reason the job failed (for example, when the processing workflow could not be started). Present only when the job has an error.
  - `next_cursor` string, uuid, nullable, required — Batch ID to pass as `cursor` for the next page, or `null` when there are no more pages.
  - `has_more` boolean, required — Whether more jobs exist after this page.

## Other responses

- `400` — Invalid query parameters
- `401` — Unauthorized — invalid or missing API key

---

[API](https://skmtc.dev/crustdata/apis/batch-api.md) · [All operations](https://skmtc.dev/crustdata/apis/batch-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/crustdata/batch-api/revisions/581689e66ae7/schema)