Reference for managing live batch jobs: checking status, downloading outputs and error files, cancelling, and listing. For an end-to-end walkthrough, see Run a batch job.Documentation Index
Fetch the complete documentation index at: https://docs.together.ai/llms.txt
Use this file to discover all available pages before exploring further.
Python examples require
together>=2.0.0Check batch status
batches.retrieve() returns the batch object directly (no .job wrapper, unlike create()).
| Status | Description |
|---|---|
VALIDATING | The input file is being validated before the batch can begin. |
IN_PROGRESS | Requests are being processed. |
COMPLETED | All requests processed; results available. |
FAILED | Processing failed. |
EXPIRED | The job exceeded its time limit. |
CANCELLED | The job was cancelled. |
Retrieve results
When the batch reachesCOMPLETED, download the output file referenced by output_file_id. Per-request failures are stored separately in error_file_id. Always download both: a COMPLETED batch can still contain individual request failures.
custom_id from your input, so you can reconcile them with a single pass over each file. Line order does not match input order.
Cancel a batch
You can cancel a batch while it isVALIDATING or IN_PROGRESS. Requests that have already completed before the cancellation are still billed, and their responses are still returned in the output file.
List batches
Errors
Error codes
| Code | Description | Solution |
|---|---|---|
| 400 | Invalid request format | Check JSONL syntax and required fields. |
| 401 | Authentication failed | Verify your API key. |
| 404 | Batch not found | Check the batch ID. |
| 429 | Rate limit exceeded | Reduce request frequency. |
| 500 | Server error | Retry with exponential backoff. |
Error file format
Each line in the error file pairs acustom_id from your input with the failure reason:
batch_errors.jsonl