KV - Deprecate legacy Workers KV namespace API routes
Key Points
- Legacy KV namespace routes deprecated Jul 15 2026
- Stop working Oct 15 2026 — migrate before then
- Replace /workers/namespaces/ with /storage/kv/namespaces/
Summary
The legacy Workers KV API routes under /accounts/{account_id}/workers/namespaces/* are deprecated as of 2026-07-15 and will stop working on 2026-10-15. Migrate to the documented routes under /accounts/{account_id}/storage/kv/namespaces/* before that date. The legacy and replacement routes are interchangeable — they accept the same request parameters and return the same response payloads.
Key Points
- Action required: update any integration that calls
/accounts/{account_id}/workers/namespaces/to use/accounts/{account_id}/storage/kv/namespaces/before 2026-10-15. - Migration is a direct URL path substitution; request parameters and response payloads remain identical.
- Common route mappings (examples):
GET/POST/accounts/{account_id}/workers/namespaces→GET/POST/accounts/{account_id}/storage/kv/namespacesGET/PUT/DELETE/accounts/{account_id}/workers/namespaces/{namespace_id}→ same under/storage/kv/namespaces/{namespace_id}GET/accounts/{account_id}/workers/namespaces/{namespace_id}/keys→ same under/storage/kv/namespaces/{namespace_id}/keysGET/accounts/{account_id}/workers/namespaces/{namespace_id}/metadata/{key_name}→ same under/storage/kv/namespaces/{namespace_id}/metadata/{key_name}GET/PUT/DELETE/accounts/{account_id}/workers/namespaces/{namespace_id}/values/{key_name}→ same under/storage/kv/namespaces/{namespace_id}/values/{key_name}
Recommended steps
- Search codebase, CI configs, and integrations for
/workers/namespaces/and replace with/storage/kv/namespaces/. - Deploy changes to staging and run API/contract tests to confirm identical behavior.
- Monitor production logs after cutover for any unexpected errors and plan a rollback window if needed.