Cloudflare API
PATCH /zones/{id}/settings endpoint removal
Stops workingSubscribe to Cloudflare APIShare
On March 31, 2027, Cloudflare will shut down the PATCH /zones/{id}/settings endpoint. This deprecation affects requests attempting to read and edit multiple zone settings in a single batch call. After this date, requests sent to PATCH /zones/{id}/settings will fail.
Calls it hits
PATCH /zones/{id}/settings
What to use instead of these calls
Use PATCH /zones/{zone_id}/settings/{setting_id} instead.
In Cloudflare API's words
The Zone Settings Batch API endpoints, which read and edit multiple zone settings in a single request, are deprecated and will reach their end of life on March 31, 2027.
Facts
- API
- Cloudflare API
api.cloudflare.com - Kind
- Endpoint removal
- Announced
- July 27, 2026
- Takes effect
- March 31, 2027
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Cloudflare API's own pages
Questions
When does this change take effect?
Calls to PATCH /zones/{id}/settings on Cloudflare API stop working on March 31, 2027.
What happens to calls after March 31, 2027?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Cloudflare API 10
-
GET /zones/{id}/amp/sxgEndpoint removal Stopped working -
PUT /client/v4/accounts/{id}/workers/scripts/{id}Behaviour change Stopped working -
GET /accounts/{id}/registrar/domainsEndpoint removal Stopped working -
GET /accounts/{id}/registrar/domains/{id}Endpoint removal Stopped working -
PUT /accounts/{id}/registrar/domains/{id}Endpoint removal Stopped working -
DELETE /accounts/{id}/teamnet/routes/network/{id}Endpoint removal Stopped working -
PATCH /accounts/{id}/teamnet/routes/network/{id}Endpoint removal Stopped working -
POST /accounts/{id}/teamnet/routes/network/{id}Endpoint removal Stopped working -
GET /zones/{id}/settingsEndpoint removal Stops workingin 145 days -
GET /radar/http/top/browserEndpoint removal Stops workingin 147 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before March 31, 2027.