Beyond the News
Sign in
Cloud & InfrastructureCloud Platforms Active dossier

Cloudflare retires its legacy Registrar API — domain-management integrations need new endpoints

Cloudflare's legacy Registrar domain-management endpoints reach end of life on September 27, 2026. Integrations that list, read or update domains through the old API need to move to the newer Registrar API surface.

Reviewed and published by Lars Jansen Updated 3 min read
Comment
First published

Key details

  1. The legacy Registrar domain-management API was deprecated April 10, 2026.
  2. Its documented end-of-life date is September 27, 2026.
  3. Affected legacy operations include list domains, get domain and update domain.
  4. Replacement operations separate domain search, availability checks, listing registrations and creating registrations.
  5. Cloudflare says integrations must migrate to avoid service interruption.

What builders should take away

  1. Search code, scripts and internal tools for the legacy `/registrar/domains` endpoints.
  2. Test domain-management automation against the replacement Registrar API before relying on it operationally.
  3. Treat registrar integrations as production dependencies: a failed renewal or provisioning workflow can have consequences well beyond an ordinary API error.

What changed

Cloudflare documented September 27, 2026 as the end-of-life date for its legacy Registrar domain-management API. The retired surface includes endpoints for listing domains, getting one domain and updating a domain. Cloudflare points developers to the newer Registrar API, including separate domain-search, domain-check, registration-list and registration-create operations.

Why it matters

Registrar automation tends to be quiet infrastructure until it fails. Scripts, internal tools and provisioning systems built around the legacy endpoints can lose domain-management functionality after the cutoff, and the replacement API changes the shape of the workflow rather than preserving the old resource paths.

The deadline is now operational rather than prospective

Cloudflare's deprecation documentation sets September 27 as the end-of-life date. Any remaining dependency on the old Registrar domain-management paths should now be treated as a compatibility risk rather than future migration work.

The replacement API changes the workflow surface

The newer Registrar API exposes domain search and availability separately from registration listing and creation. Builders should map what their existing automation actually does instead of assuming an endpoint-for-endpoint substitution.

What to watch next

  • Whether Cloudflare publishes post-cutoff compatibility guidance or migration issues.
  • Reports from Terraform or registrar-automation users still depending on legacy paths.

Still unclear

  • Cloudflare's deprecation page states the cutoff and replacements but does not describe every post-EOL failure mode for legacy calls.
  • The documented replacement list does not imply that every legacy update workflow has a one-to-one equivalent without application changes.

Sources

Direct reading behind this dossier.

1 sources
API deprecations
Cloudflare primary documentation

Documents legacy Registrar API deprecation, September 27 EOL and replacement endpoints.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment
Continue reading
Web Development

Cloudflare’s new cf CLI gives coding agents access to its entire API

The interesting change is not another CLI rename. Cloudflare is redesigning its command surface around software agents: JSON is the default, commands can be discovered through natural-language search, configuration is typed TypeScript, and Wrangler now has an eventual migration path.