Registrar compatibility for Account API Tokens appears to be outdated

[CQMHV]

Existing documentation URL(s)

https://developers.cloudflare.com/fundamentals/api/get-started/account-owned-tokens/

https://developers.cloudflare.com/registrar/registrar-api/

What changes are you suggesting?

The Account API Token compatibility matrix currently lists Registrar as unsupported (❌).

However, this does not appear to match the current Dashboard or API behavior.

The Account API Token creation interface currently exposes both of the following permissions:

Registrar Domains: Admin
Registrar Sandbox Domains: Admin

Using an account-owned API token (cfat_...) scoped to a specific account with these permissions, I was able to successfully authenticate to multiple production Registrar endpoints and complete a registration workflow in the Registrar Sandbox.

Could you clarify whether:

1. Registrar now supports Account API Tokens and the compatibility matrix is outdated, or
2. Account API Token support is currently limited to only a subset of Registrar functionality?

If Registrar now supports Account API Tokens, the compatibility matrix should be updated accordingly.

If support is only partial, it would be helpful for the documentation to specify which Registrar endpoints or operations support Account API Tokens.

Additional information

I tested the following endpoints using the same account-owned cfat_... token:

Endpoint	Result
GET /accounts/{account_id}/tokens/verify	✅ Success
POST /accounts/{account_id}/registrar/domain-check	✅ Success
GET /accounts/{account_id}/registrar/registrations?per_page=1	✅ Success
GET /accounts/{account_id}/registrar/extensions/com	✅ Success
POST /accounts/{account_id}/registrar-sandbox/domain-check	✅ Success
GET /accounts/{account_id}/registrar-sandbox/extensions/com	✅ Success
POST /accounts/{account_id}/registrar-sandbox/registrations	✅ Success

The production domain-check endpoint returned domain availability, tier, and registration/renewal pricing as expected.

The production registrar/registrations endpoint successfully returned an existing domain registration from the account.

The production registrar/extensions/com endpoint successfully returned the .com registration schema.

In the Registrar Sandbox, domain availability and extension schema retrieval both succeeded. A sandbox registration write operation also completed successfully:

{
    "success": true,
    "result": {
        "state": "succeeded",
        "completed": true
    }
}

This indicates that Account API Tokens are accepted not only for availability checks and read operations, but also for at least one Registrar registration write workflow in the Sandbox.

I intentionally did not test the production registration endpoint:

POST /accounts/{account_id}/registrar/registrations

solely for the purpose of verifying token compatibility, since a successful production registration would incur a real, non-refundable domain registration charge.

The equivalent registration workflow was instead verified successfully using the Registrar Sandbox.