One change
Retrieve a Message Batch
api/beta/messages/batches/retrieve
Nearest release: v2.1.245, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
api/beta/messages/batches/retrieve Changed · +34 / -19 lines
# Retrieve a Message Batch ## Path parameters ## Headers ## Returns ## Example ### Response (200) ## Retrieve a Message Batch ### Path Parameters ### Header Parameters ### Returns ### Example #### Response
from line 1
---- -title: Retrieve a Message Batch -url: https://platform.claude.com/docs/en/api/beta/messages/batches/retrieve ---- +# Retrieve a Message Batch -## Retrieve a Message Batch +**GET** `/v1/messages/batches/{message_batch_id}` -**get** `/v1/messages/batches/{message_batch_id}` - This endpoint is idempotent and can be used to poll for Message Batch completion. To access the results of a Message Batch, make a request to the `results_url` field in the response. Learn more about the Message Batches API in our [user guide](https://platform.claude.com/docs/en/build-with-claude/batch-processing) -### Path Parameters +## Path parameters - `message_batch_id: string` ID of the Message Batch. -### Header Parameters +## Headers - `"anthropic-beta": optional array of AnthropicBeta`
from line 90
- `"mid-conversation-tool-changes-2026-07-01"` -### Returns +## Returns -- `BetaMessageBatch object { id, archived_at, cancel_initiated_at, 7 more }` +- `BetaMessageBatch object` - `id: string`
from line 104
RFC 3339 datetime string representing the time at which the Message Batch was archived and its results became unavailable. + format: date-time + - `cancel_initiated_at: string or null` RFC 3339 datetime string representing the time at which cancellation was initiated for the Message Batch. Specified only if cancellation was initiated. + format: date-time + - `created_at: string` RFC 3339 datetime string representing the time at which the Message Batch was created. + format: date-time + - `ended_at: string or null` RFC 3339 datetime string representing the time at which processing for the Message Batch ended. Specified only once processing ends.
from line 124
Processing ends when every request in a Message Batch has either succeeded, errored, canceled, or expired. + format: date-time + - `expires_at: string` RFC 3339 datetime string representing the time at which the Message Batch will expire and end processing, which is 24 hours after creation. + format: date-time + - `processing_status: "in_progress" or "canceling" or "ended"` Processing status of the Message Batch.
from line 154
This is zero until processing of the entire Message Batch has ended. + default: 0 + - `errored: number` Number of requests in the Message Batch that encountered an error.
from line 162
This is zero until processing of the entire Message Batch has ended. + default: 0 + - `expired: number` Number of requests in the Message Batch that have expired.
from line 170
This is zero until processing of the entire Message Batch has ended. + default: 0 + - `processing: number` Number of requests in the Message Batch that are processing. + default: 0 + - `succeeded: number` Number of requests in the Message Batch that have completed successfully.
from line 184
This is zero until processing of the entire Message Batch has ended. + default: 0 + - `results_url: string or null` URL to a `.jsonl` file containing the results of the Message Batch requests. Specified only once processing ends.
from line 198
For Message Batches, this is always `"message_batch"`. - - `"message_batch"` + default: message_batch -### Example +## Example -```http +```bash curl https://api.anthropic.com/v1/messages/batches/$MESSAGE_BATCH_ID \ -H 'anthropic-version: 2023-06-01' \ -H 'anthropic-beta: message-batches-2024-09-24' \
from line 209
-H "X-Api-Key: $ANTHROPIC_API_KEY" ``` -#### Response +### Response (200) ```json {