API
Cloudflare
The old /workers/namespaces/ REST API paths for managing Workers KV stop working; calls must move to the /storage/kv/namespaces/ paths
departs 15 Oct 2026
Quick answers
- Is it true that Cloudflare retires the legacy Workers KV namespace API routes?
- Yes. Cloudflare has officially announced it, effective 15 Oct 2026. This affects anything that manages Cloudflare Workers KV namespaces through Cloudflare's REST API on the older URL — CI/CD scripts, infrastructure-as-code, deployment tooling, and any custom automation that calls the /accounts/{account_id}/workers/namespaces/* endpoints.
- When does it take effect?
- 15 Oct 2026. Verified against the vendor's own announcement.
- What should I use instead?
- Update the base path in any code that hits the KV namespace API: change /accounts/{account_id}/workers/namespaces/ to /accounts/{account_id}/storage/kv/namespaces/.
What this means for you
This affects anything that manages Cloudflare Workers KV namespaces through Cloudflare's REST API on the older URL — CI/CD scripts, infrastructure-as-code, deployment tooling, and any custom automation that calls the /accounts/{account_id}/workers/namespaces/* endpoints. Per Cloudflare's own deprecations page, after 15 October 2026 requests to those legacy routes will no longer be supported. Interactive use through the dashboard and Wrangler is not what this is about; the sharp edge is automation that hardcodes the old path and will start failing once the routes are gone. The good news is that this is a path rename, not a behaviour change: Cloudflare states the legacy and replacement routes are interchangeable — same request parameters, same response payloads — so nothing about how you call the API changes except the URL.
Where to go
Update the base path in any code that hits the KV namespace API: change /accounts/{account_id}/workers/namespaces/ to /accounts/{account_id}/storage/kv/namespaces/. Because Cloudflare says the two route sets accept the same parameters and return the same payloads, this is a find-and-replace on the URL prefix rather than a rewrite — but do it before 15 October 2026, and check generated clients, SDK versions, and any vendored API wrappers that may still target the old path. This is one of several endpoint end-of-life dates Cloudflare has scheduled on the same page; a related one worth noting if you use Cloudflare-managed DNS is the Foundation DNS boolean setting, which the DNS settings API stops returning or accepting beginning 23 November 2026.
- The replacement Workers KV routes at /accounts/{account_id}/storage/kv/namespaces/ (same parameters and responses)
- Manage KV via the Cloudflare dashboard or the Wrangler CLI, which are unaffected by this API path change
Cloudflare has set an end-of-life date for the original REST API paths used to manage Workers KV namespaces. On Cloudflare’s API deprecations page, the company states that after 15 October 2026, requests to the legacy /accounts/{account_id}/workers/namespaces/* routes will no longer be supported. The functionality is not going away — it is moving to a new address under Cloudflare’s consolidated storage API.
The part that matters is who calls these routes. This is not the Workers KV feature shutting down, and it is not something a dashboard user or a current wrangler release will notice. It is a break for automation: CI/CD pipelines, infrastructure-as-code, and bespoke scripts that create, list, or delete KV namespaces by calling the old URL directly. Anything with the legacy path baked in stops working on the date, returning errors instead of managing your namespaces.
Fixing it is deliberately cheap. Cloudflare says the legacy and replacement routes are interchangeable — they take the same parameters and return the same payloads — so the migration is a single change to the base path: swap /accounts/{account_id}/workers/namespaces/ for /accounts/{account_id}/storage/kv/namespaces/. The work is finding every place the old prefix is hardcoded: generated API clients, older SDK pins, and copied-in wrapper code are the usual hiding spots. Make the change before 15 October 2026 and there is nothing else to do; miss it and the failure shows up as broken deploys rather than a graceful warning.
This is one of a cluster of endpoint end-of-life dates Cloudflare lists on the same page. If you run Cloudflare-managed DNS, the one to also flag is the Foundation DNS boolean setting: beginning 23 November 2026, Cloudflare’s DNS settings API stops returning or accepting the foundation_dns field, with configuration moving to the newer advanced-nameservers model instead.
Entry changelog
- — last reviewed.
- — Entry created from Cloudflare's official API deprecations page (developers.cloudflare.com/fundamentals/api/reference/deprecations). EOL date 15 October 2026 and the /workers/namespaces/ → /storage/kv/namespaces/ path change quoted from that page; sibling Foundation DNS deprecation (23 November 2026) noted from the same source.
- — Added a detect: fingerprint (text:/workers/namespaces/) so the lastcall CLI flags code still calling the legacy Workers KV routes. No facts changed — the pattern is the deprecated path segment from the source and will not match the /storage/kv/namespaces/ replacement.
Put this countdown in your README
Building on Cloudflare? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/cloudflare-workers-kv-legacy-api-eol)Spot an error or a changed date? Tell us and it’s corrected the same night.