List Message Batches
get /v1/messages/batches
List all Message Batches within a Workspace. Most recently created batches are returned first.
Learn more about the Message Batches API in our user guide
Query Parameters
-
after_id: optional stringID of the object to use as a cursor for pagination. When provided, returns the page of results immediately after this object.
-
before_id: optional stringID of the object to use as a cursor for pagination. When provided, returns the page of results immediately before this object.
-
limit: optional numberNumber of items to return per page.
Defaults to
20. Ranges from1to1000.
Returns
-
data: array of MessageBatch-
id: stringUnique object identifier.
The format and length of IDs may change over time.
-
archived_at: stringRFC 3339 datetime string representing the time at which the Message Batch was archived and its results became unavailable.
-
cancel_initiated_at: stringRFC 3339 datetime string representing the time at which cancellation was initiated for the Message Batch. Specified only if cancellation was initiated.
-
created_at: stringRFC 3339 datetime string representing the time at which the Message Batch was created.
-
ended_at: stringRFC 3339 datetime string representing the time at which processing for the Message Batch ended. Specified only once processing ends.
Processing ends when every request in a Message Batch has either succeeded, errored, canceled, or expired.
-
expires_at: stringRFC 3339 datetime string representing the time at which the Message Batch will expire and end processing, which is 24 hours after creation.
-
processing_status: "in_progress" or "canceling" or "ended"Processing status of the Message Batch.
-
"in_progress" -
"canceling" -
"ended"
-
-
request_counts: MessageBatchRequestCountsTallies requests within the Message Batch, categorized by their status.
Requests start as
processingand move to one of the other statuses only once processing of the entire batch ends. The sum of all values always matches the total number of requests in the batch.-
canceled: numberNumber of requests in the Message Batch that have been canceled.
This is zero until processing of the entire Message Batch has ended.
-
errored: numberNumber of requests in the Message Batch that encountered an error.
This is zero until processing of the entire Message Batch has ended.
-
expired: numberNumber of requests in the Message Batch that have expired.
This is zero until processing of the entire Message Batch has ended.
-
processing: numberNumber of requests in the Message Batch that are processing.
-
succeeded: numberNumber of requests in the Message Batch that have completed successfully.
This is zero until processing of the entire Message Batch has ended.
-
-
results_url: stringURL to a
.jsonlfile containing the results of the Message Batch requests. Specified only once processing ends.Results in the file are not guaranteed to be in the same order as requests. Use the
custom_idfield to match results to requests. -
type: "message_batch"Object type.
For Message Batches, this is always
"message_batch"."message_batch"
-
-
first_id: stringFirst ID in the
datalist. Can be used as thebefore_idfor the previous page. -
has_more: booleanIndicates if there are more results in the requested page direction.
-
last_id: stringLast ID in the
datalist. Can be used as theafter_idfor the next page.
Example
curl https://api.anthropic.com/v1/messages/batches \
-H 'anthropic-version: 2023-06-01' \
-H "X-Api-Key: $ANTHROPIC_API_KEY"
Response
{
"data": [
{
"id": "msgbatch_013Zva2CMHLNnXjNJJKqJ2EF",
"archived_at": "2024-08-20T18:37:24.100435Z",
"cancel_initiated_at": "2024-08-20T18:37:24.100435Z",
"created_at": "2024-08-20T18:37:24.100435Z",
"ended_at": "2024-08-20T18:37:24.100435Z",
"expires_at": "2024-08-20T18:37:24.100435Z",
"processing_status": "in_progress",
"request_counts": {
"canceled": 10,
"errored": 30,
"expired": 10,
"processing": 100,
"succeeded": 50
},
"results_url": "https://api.anthropic.com/v1/messages/batches/msgbatch_013Zva2CMHLNnXjNJJKqJ2EF/results",
"type": "message_batch"
}
],
"first_id": "first_id",
"has_more": true,
"last_id": "last_id"
}