List All Batches
List batches across the organization. The X-Namespace header narrows the list to that namespace, exactly like every other namespaced endpoint; omit it for the org-wide view. namespace_id in the request body also works (and wins ties when it agrees with the header; a conflicting header + body is a 400). Other body filters: status, bucket_id, collection_id.
Authorizations
Mixpeek API key, sent as Authorization: Bearer mxp_sk_.... Create one in Studio under Settings → API Keys, or with an admin key via POST /v1/organizations/users/{user_email}/api-keys. A missing header returns 403; an invalid or revoked key returns 401.
Body
The request model for listing batches.
Filter batches by status.
PENDING, QUEUED, IN_PROGRESS, PROCESSING, COMPLETED, COMPLETED_WITH_ERRORS, FAILED, CANCELED, INTERRUPTED, UNKNOWN, SKIPPED, DRAFT, ACTIVE, ARCHIVED, SUSPENDED, DEACTIVATED Filter batches to only those associated with a specific collection ID. Useful for tracking the processing state of all batches for a given collection.
Filter batches to only those belonging to a specific bucket. Useful with the org-level POST /v1/batches/list endpoint to scope results.
Filter batches to a single namespace. Required here because POST /v1/batches/list is organization-scoped and does NOT read the X-Namespace header — that header is ignored on this endpoint, so pass the namespace here to narrow results.
The number of batches to skip.
x >= 0The maximum number of batches to return.
1 <= x <= 1000Cursor for deep pagination. Use next_cursor from a previous response to fetch the next page. More efficient than offset for large result sets.
Response
Successful Response
The response model for listing batches.
Each batch in results includes bucket_id, enabling callers to build batch-to-bucket mappings without additional queries.

