API
Cloudflare
The legacy Cloudflare Registrar domain-management API paths (/accounts/{account_id}/registrar/domains) stop working; automation that manages Cloudflare-registered domains must move to the new Registrar API
departs 27 Sept 2026
Quick answers
- Is it true that Cloudflare retires the legacy Registrar API — the /registrar/domains endpoints reach end-of-life 27 September 2026?
- Yes. Cloudflare has officially announced it, effective 27 Sept 2026. This affects anything that manages Cloudflare Registrar domains through Cloudflare's REST API on the older path — infrastructure-as-code, domain-portfolio automation, billing/renewal scripts, and any custom tooling that calls the legacy /accounts/{account_id}/registrar/domains endpoints.
- When does it take effect?
- 27 Sept 2026. Verified against the vendor's own announcement.
- What should I use instead?
- Move any code that calls /accounts/{account_id}/registrar/domains to the new Registrar API (developers.cloudflare.com/api/resources/registrar/).
What this means for you
This affects anything that manages Cloudflare Registrar domains through Cloudflare's REST API on the older path — infrastructure-as-code, domain-portfolio automation, billing/renewal scripts, and any custom tooling that calls the legacy /accounts/{account_id}/registrar/domains endpoints. Per Cloudflare's own deprecations page, the legacy Registrar API was deprecated on 10 April 2026 and reaches end-of-life on 27 September 2026, after which those calls are no longer supported. The Registrar feature itself is not going away — Cloudflare has published a new Registrar API in its place, with endpoints for domain search, availability checking, registration, and management. As with Cloudflare's other endpoint retirements, the sharp edge is unattended automation: a dashboard user renewing a domain by hand sees nothing change, but a script that lists or updates domains by hitting the old URL will start returning errors on the date. Anyone who registers or transfers domains through Cloudflare Registrar and drives it via the API should assume they are in scope until they have checked.
Where to go
Move any code that calls /accounts/{account_id}/registrar/domains to the new Registrar API (developers.cloudflare.com/api/resources/registrar/). Because the new API is a re-shaped resource rather than a pure path rename, budget a little more than a find-and-replace: confirm the request and response shapes for the operations you use (listing domains, reading a domain, updating auto-renew or nameserver settings) against the new reference, then update generated clients, vendored wrappers, and any Terraform or CI steps that touch domains. Do it before 27 September 2026. This is one of a cluster of endpoint end-of-life dates Cloudflare lists on the same page — if you authenticate API calls with the legacy X-Auth-User-Service-Key header, note the separate Service Key authentication retirement on 30 September 2026, three days later.
- The new Cloudflare Registrar API at developers.cloudflare.com/api/resources/registrar/ (domain search, availability, registration, and management)
- Manage domains through the Cloudflare dashboard, which is unaffected by this API path retirement
Cloudflare has set an end-of-life date for the original REST API used to manage domains registered through Cloudflare Registrar. On Cloudflare’s API deprecations page, the company lists the legacy Registrar API as deprecated on 10 April 2026 with an end-of-life date of 27 September 2026. The affected paths are the old /accounts/{account_id}/registrar/domains endpoints; after the date, requests to them are no longer supported.
The feature is not being retired — only the old address for it. Cloudflare has published a new Registrar API in its place, with endpoints for searching domains, checking availability, registering, and managing existing registrations. So this is a migration, not a shutdown: the ability to automate domain management stays, but the code that does it has to move.
As with the rest of Cloudflare’s scheduled endpoint retirements, the risk sits entirely in automation rather than in interactive use. Someone renewing a domain by hand in the dashboard will not notice a thing. What breaks is anything that manages Cloudflare-registered domains by calling the legacy URL directly — infrastructure-as-code that reconciles a domain portfolio, renewal or transfer scripts, billing exports, and bespoke tooling that lists or updates domains through the old path. On 27 September 2026 those calls start returning errors instead of doing their job, and the failure shows up as a broken pipeline rather than a warning.
Fixing it means pointing that code at the new Registrar API and checking the shapes, because this is a re-designed resource rather than a straight path rename. Confirm the request and response formats for the operations you actually use against the new reference, then update generated clients, vendored API wrappers, and any Terraform or CI steps that touch domains — all before 27 September 2026.
This is one of a cluster of end-of-life dates Cloudflare has scheduled on the same page. If your API calls authenticate with the legacy X-Auth-User-Service-Key header, the one to flag right after this is Service Key authentication, which reaches end-of-life on 30 September 2026 — three days after the Registrar API, and a separate migration to Cloudflare API Tokens.
Entry changelog
- — last reviewed.
- — Entry created from Cloudflare's official API deprecations page (developers.cloudflare.com/fundamentals/api/reference/deprecations). Deprecation date 10 April 2026, end-of-life 27 September 2026, the affected /accounts/{account_id}/registrar/domains endpoints, and the new Registrar API replacement all quoted from that page. Added a detect: fingerprint (text:/registrar/domains) so the lastcall CLI flags code still calling the legacy Registrar routes; the pattern is the deprecated path segment and does not match the new Registrar API resource paths.
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-legacy-registrar-api-eol)Spot an error or a changed date? Tell us and it’s corrected the same night.