ST-2026-091 · API endpoints & versions
Cloudflare extends the Zone Settings Batch API end-of-life date
Cloudflare extended the Zone Settings Batch API end-of-life date from 15 September 2026 to 31 March 2027; callers must migrate from the batch GET/PATCH routes to per-setting endpoints before the new deadline.
Previous state
The Zone Settings Batch API was previously scheduled to reach end of life on 15 September 2026.
Current state
The deprecated GET /zones/{zone_id}/settings and PATCH /zones/{zone_id}/settings batch routes are now scheduled to reach end of life on 31 March 2027. Cloudflare directs callers to the corresponding per-setting GET and PATCH endpoints.
Affected users
Who needs to care
Integrations that read or edit multiple zone settings through GET /zones/{zone_id}/settings or PATCH /zones/{zone_id}/settings.
Required response
What to do
Migrate to the per-setting GET /zones/{zone_id}/settings/{setting_id} and PATCH /zones/{zone_id}/settings/{setting_id} endpoints before 31 March 2027, and test multi-setting workflows against the resulting per-setting request pattern.
Evidence boundary
What the source does not prove
This is an extension of the existing Zone Settings Batch API deprecation deadline, not a new deprecation; the cited Cloudflare notice establishes the old and new end-of-life dates and the per-setting replacement routes.
Lifecycle history
Dated event sequence
- End-of-life extension published
Cloudflare extended the Zone Settings Batch API end-of-life date from 15 September 2026 to 31 March 2027 and directed callers to per-setting endpoints.
- Zone Settings Batch API end of life
The deprecated batch GET and PATCH endpoints are scheduled to become unavailable after this date.
Evidence ledger
First-party sources
- 01Cloudflare — API deprecations — Zone Settings Batch API
Official Cloudflare API deprecation notice · 2026-07-27
Open official source ↗