Retrieve the status of a batch run by its ID. The status field reflects the aggregate state of the batch.
This is a unified endpoint that works for batches created via any of the batch submission endpoints (POST /parse_runs/batch, POST /extract_runs/batch, POST /classify_runs/batch, POST /split_runs/batch).
To retrieve individual run results, use the List endpoint for the relevant type filtered by batchId:
GET /parse_runs?batchId={id}GET /extract_runs?batchId={id}GET /classify_runs?batchId={id}GET /split_runs?batchId={id}Bearer authentication of the form Bearer <token>, where token is your auth token.
The unique identifier of the batch processor run to retrieve.
Example: "bpr_Xj8mK2pL9nR4vT7qY5wZ"
The type of object. Always "batch_run".
The unique identifier for this batch run.
Example: "bpr_Xj8mK2pL9nR4vT7qY5wZ"
The status of a batch run:
"PENDING" - The batch has been created and is waiting to be processed"PROCESSING" - The batch is currently being processed"PROCESSED" - All runs in the batch have completed successfully"FAILED" - The batch failed to process"CANCELLED" - The batch was cancelledThe time (in UTC) at which the object was created. Will follow the RFC 3339 format.
Example: "2024-03-21T16:45:00Z"
API version to use for the request. If you’re using an SDK, you can ignore this parameter. If you are not using an SDK and do not specify a version, you will either receive a 400 Bad Request or be set to a previous legacy version. See API Versioning for more details.