# 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.

The replacement is not a drop-in path rename: Cloudflare separates domain search, availability checks and registration operations into newer endpoints, so old registrar automation can break after the cutoff.

- Status: Active
- Published: 2026-09-27T22:44:31+13:00
- Updated: 2026-09-27T22:44:31+13:00
- Categories: Cloud & Infrastructure, Cloud Platforms
- Tags: API deprecation, API migration, Cloudflare, domain registration
- Canonical HTML: https://beyondthe.news/dossiers/cloudflare-registrar-legacy-api-eol-september-27-2026

## 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.

## Key details

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

## Builder takeaways

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

## What to watch

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

## Uncertainties

- 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

- [API deprecations](https://developers.cloudflare.com/fundamentals/api/reference/deprecations/) — Cloudflare · primary documentation · 2026-09-27T00:00:00+12:00. Documents legacy Registrar API deprecation, September 27 EOL and replacement endpoints.