Message Batches API changedbuild-with-claude/batch-processing
Recorded here
Lines+60added
Lines−10removed
From line
2
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits29to this page, all time
## Availability ### API support #### [Messages API](https://platform.claude.com/docs/en/build-with-claude/working-with-messages) #### [Managed Agents](https://platform.claude.com/docs/en/managed-agents/overview) ### Data handling ## Data retention
The whole hunk
from line 2, old and new numbered
/
from line 2
22title: Batch processing
33url: https://platform.claude.com/docs/en/build-with-claude/batch-processing
44description: Process large volumes of Messages requests asynchronously with the Message Batches API, cutting costs by 50 percent and increasing throughput.
5featureMetadata:
6 status: ga
7 zdr:
8 eligibility: not-eligible
9 note: 29-day retention; async storage required.
10 supportedModels:
11 - claude-fable-5-1
12 - claude-mythos-5-1
13 - claude-fable-5
14 - claude-mythos-5
15 - claude-mythos-preview
16 - claude-opus-5-5
17 - claude-opus-5
18 - claude-sonnet-5-5
19 - claude-sonnet-5
20 - claude-haiku-5-5
21 - claude-haiku-4-5-20251001
22 - claude-opus-4-8
23 - claude-opus-4-7
24 - claude-opus-4-6
25 - claude-sonnet-4-6
26 - claude-opus-4-5-20251101
27 - claude-sonnet-4-5-20250929
28 supportedPlatforms:
29 Claude API: ga
30 Claude Platform on AWS: ga
31 Claude Models on Google Cloud (Anthropic managed): ga
532---
633
734Batch processing is a powerful approach for handling large volumes of requests efficiently. Instead of processing requests one at a time with immediate responses, batch processing allows you to submit multiple requests together for asynchronous processing. This pattern is particularly useful when:
from line 40
1340
1441The Message Batches API is Anthropic’s first implementation of this pattern.
1542
16<Note>
17 To learn how zero data retention (ZDR) applies to this feature, see [API and data retention](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention).
18</Note>
19
2043# Message Batches API
2144
2245The Message Batches API is a powerful, cost-effective way to asynchronously process large volumes of [Messages](https://platform.claude.com/docs/en/api/messages/create) requests. This approach is well-suited to tasks that do not require immediate responses, with most batches finishing in less than 1 hour while reducing costs by 50 percent and increasing throughput.
from line 1839
18161839
18171840* **Result availability:** Batch results are available for 29 days after the batch is created, allowing ample time for retrieval and processing.
18181841
1819## Data retention
1820
1821Batch processing stores request and response data for up to 29 days after batch creation. You can delete a message batch at any time after processing using the [`DELETE /v1/messages/batches/{batch_id}`](https://platform.claude.com/docs/en/api/messages/batches/delete) endpoint. To delete an in-progress batch, cancel it first. Asynchronous processing requires server-side storage of both inputs and outputs until batch completion and result retrieval.
1822
1823For ZDR eligibility across all features, see [API and data retention](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention).
1824
18251842## FAQ
18261843
18271844<AccordionGroup>
from line 1883
18661883 Yes, it is possible to use prompt caching with the Message Batches API. However, because asynchronous batch requests can be processed concurrently and in any order, cache hits are provided on a best-effort basis.
18671884 </Accordion>
18681885</AccordionGroup>
1886
1887## Availability
1888
1889Batch processing is available on every model.
1890
1891### API support
1892
1893#### [Messages API](https://platform.claude.com/docs/en/build-with-claude/working-with-messages)
1894
1895* Availability: Available
1896
1897| Status | Cloud platforms |
1898| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
1899| Available | Claude API, [Claude Platform on AWS](https://platform.claude.com/docs/en/build-with-claude/claude-platform-on-aws), [Claude Models on Google Cloud (Anthropic managed)](https://platform.claude.com/docs/en/build-with-claude/claude-models-on-google-cloud/anthropic-managed) |
1900
1901#### [Managed Agents](https://platform.claude.com/docs/en/managed-agents/overview)
1902
1903* Availability: Not available
1904
1905### Data handling
1906
1907[Data handling overview](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention#feature-eligibility)
1908
1909| Item | Zero data retention | HIPAA |
1910| ------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |
1911| Status | Not eligible | Not eligible |
1912| Details | 29-day retention; async storage required. [Learn more](https://platform.claude.com/docs/en/build-with-claude/batch-processing#data-retention) | — |
1913
1914Applicable endpoints:
1915
1916* `/v1/messages/batches`
1917
1918Batch processing stores request and response data for up to 29 days after batch creation. You can delete a message batch at any time after processing using the [`DELETE /v1/messages/batches/{batch_id}`](https://platform.claude.com/docs/en/api/messages/batches/delete) endpoint. To delete an in-progress batch, cancel it first. Asynchronous processing requires server-side storage of both inputs and outputs until batch completion and result retrieval.
18691919
18701920## Next steps
18711921
No line in this hunk matches that.