Cloudflare API
GET /zones/{id}/amp/sxg endpoint removal
Stopped workingSubscribe to Cloudflare APIShare
Calls to GET /zones/{id}/amp/sxg on Cloudflare API stopped working on June 23, 2026.
Calls it hits
GET /zones/{id}/amp/sxg
In Cloudflare API's words
The AMP/SXG features have reached end of life. There will be no replacement functionality.
Facts
- API
- Cloudflare API
api.cloudflare.com - Kind
- Endpoint removal
- Announced
- September 18, 2025
- Takes effect
- June 23, 2026
- 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 GET /zones/{id}/amp/sxg on Cloudflare API stopped working on June 23, 2026.
What happens to calls after June 23, 2026?
They have failed since June 23, 2026.
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 /accounts/{id}/devicesEndpoint removal Stopped working -
GET /accounts/{id}/devices/{id}Endpoint removal Stopped working -
PUT /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
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.