Cloudflare's July 2026 API Deprecation Wave: Full Guide

A dark comparison-matrix style cover listing Cloudflare's July 2026 API deprecations: legacy Workers KV routes, Zero Trust CIDR route endpoints, Tunnel connections field, Zone Settings Batch API, and the 65-character account name limit
On this page

Structural Comparison Matrix

#DeprecationAPI surfaceDeadlineStatus
1Legacy Workers KV namespace routes/accounts/{account_id}/workers/namespaces/*2026-10-15Upcoming
2Zero Trust CIDR route endpointsZero Trust Networks routes API2026-10-05Upcoming
3connections field dropped from Tunnel APITunnel/Mesh list and get responses2026-10-05Upcoming
4Zone Settings Batch API/zones/{zone_id}/settings (batch)2026-09-15Upcoming
565-character account name limit enforcedAccount creation/update APIs2026-09-27Upcoming
6foundation_dns settingDNS settings endpoints2026-11-23Upcoming
7Account Roles API/accounts/{account_id}/roles2026-07-21 (no published EOL yet)Deprecated
8AMP/SXG API/zones/{zone_id}/amp/sxg2026-06-23Already ended
9Legacy Registrar domain API/accounts/{account_id}/registrar/domains2026-09-27Upcoming
10Gateway Audit SSH rulesGateway network policy audit_ssh action2026-07-15Already ended

Every deadline above is Cloudflare’s own stated date, cross-checked against its official changelog entry for that deprecation. Two (AMP/SXG and Gateway Audit SSH) already reached end of life before this guide was published - if automation calling either has been failing with no obvious cause, that is why.

The 10 deprecations, in detail

  1. Cloudflare Deprecates Legacy Workers KV API Routes: the legacy /workers/namespaces/* routes stop 2026-10-15. This site’s own KV bindings are the dogfooded example.
  2. Cloudflare Removes Zero Trust CIDR Route Endpoints: CIDR-encoded Tunnel/WARP Connector routing goes away 2026-10-05.
  3. Cloudflare Drops connections Field From Tunnel API: a schema change on the same 2026-10-05 date, distinct from cluster 2: a missing response field, not a removed endpoint.
  4. Cloudflare Deprecates the Zone Settings Batch API: batched zone-settings reads/writes end 2026-09-15; migrate to per-setting calls.
  5. Cloudflare Now Enforces a 65-Char Account Name Limit: a new validation constraint on account creation/rename APIs, effective 2026-09-27.
  6. Cloudflare Deprecates the foundation_dns DNS Setting: the foundation_dns boolean stops working 2026-11-23.
  7. Cloudflare Deprecates the Account Roles API: already in effect since 2026-07-21; migrate to the Permission Groups API, a genuinely different data model.
  8. Cloudflare AMP/SXG API Has Reached End of Life: already ended 2026-06-23, with no replacement.
  9. Cloudflare Deprecates Legacy Registrar Domain API: domain registration/renewal automation loses its endpoint 2026-09-27.
  10. Cloudflare Deprecates Gateway Audit SSH Rules: a staged rollout that fully ended 2026-07-15, three separate dates where a policy-as-code pipeline could have quietly broken.

Why this happened in one window

Cloudflare is consolidating storage APIs under a unified /storage/ namespace and tightening validation across account management, alongside routine Zero Trust and Gateway feature retirements. None of the dates or endpoint paths above are estimated - they come directly from Cloudflare’s official API deprecations reference and its changelog, cross-checked per cluster against the individual changelog post.

Browse the rest of the Data Automation archive for more Cloudflare API and pipeline coverage.

Frequently asked

Do all 10 of these deprecations affect every Cloudflare account?

No. Each one only bites if your automation actually calls that specific API surface: Workers KV bindings, Zero Trust Tunnel/Mesh, zone settings batch calls, account creation scripts, DNS settings toggles, role enumeration, AMP/SXG, domain registrar automation, or Gateway audit_ssh policies. Check the table below against what your own scripts and Terraform configs actually call.

Which of these are already in effect, not just upcoming?

Two: the AMP/SXG API reached end of life 2026-06-23, and Gateway's audit_ssh action fully stopped working 2026-07-15, both before this guide was published. If automation calling either has been silently failing with no obvious cause, that's why - see clusters 8 and 10 below for the exact staged timelines.

Emitted as FAQPage JSON-LD from the same frontmatter — one source, no duplicated prose.

Recent posts

Full-text search via Pagefind · ↑↓ to navigate · ↵ to open