List all accounts you have ownership or verified access to. Read operation.

Lists, searches, sorts, and filters your zones. Listing zones across more than 500 accounts is currently not allowed. Read operation.

Retrieves detailed information about a specific zone identified by its zone ID.

Returns zone configuration, status, nameservers, and associated metadata. Read operation.

List, search, sort, and filter a zones' DNS records. Read operation.

Retrieves details for a specific DNS record in the zone. Read operation.

Create a new DNS record for a zone.

Notes:

• A/AAAA records cannot exist on the same name as CNAME records.

• NS records cannot exist on the same name as any other record type.

• Domain names are always represented in Punycode, even if Unicode characters were used when creating the record. Every change requires explicit confirmation; never repeat an unknown outcome automatically.

Update an existing DNS record.

Notes:

• A/AAAA records cannot exist on the same name as CNAME records.

• NS records cannot exist on the same name as any other record type.

• Domain names are always represented in Punycode, even if Unicode characters were used when creating the record. Every change requires explicit confirmation; never repeat an unknown outcome automatically.

Overwrite an existing DNS record.

Notes:

• A/AAAA records cannot exist on the same name as CNAME records.

• NS records cannot exist on the same name as any other record type.

• Domain names are always represented in Punycode, even if Unicode characters were used when creating the record. Every change requires explicit confirmation; never repeat an unknown outcome automatically.

Permanently removes a DNS record from the zone. Every change requires explicit confirmation; never repeat an unknown outcome automatically.

Send a Batch of DNS Record API calls to be executed together.

Notes:

• Although Cloudflare will execute the batched operations in a single database transaction, Cloudflare's distributed KV store must treat each record change as a single key-value pair. This means that the propagation of changes is not atomic. See the documentation for more information.

• The operations you specify within the /batch request body are always executed in the following order:

  • Deletes

  • Patches

  • Puts

  • Posts Every change requires explicit confirmation; never repeat an unknown outcome automatically.

Deletes cached content in every Cloudflare data center and cache tier, including Cache Reserve. The next request for purged content is a cache MISS: Cloudflare fetches the full response from your origin and caches it again. Cloudflare does not serve purged content from cache again, even if your origin is unavailable.

To keep content cached and have Cloudflare revalidate it with your origin instead, use POST /zones/{zone_id}/invalidate_cache.

Choose what to purge

Send one of these fields in the request body:

• files: specific URLs. If your cache key includes request headers, send each URL with the header values it was cached with.

• tags: all content whose Cache-Tag response header contains one of the tags.

• hosts: all content cached for the hostnames.

• prefixes: all content whose URL starts with one of the prefixes.

• purge_everything: all cached content in the zone.

Check the result

A 200 response with success: true means Cloudflare accepted the request. It does not confirm that any content was cached or removed. To check, request a purged URL and confirm that the CF-Cache-Status response header is MISS.

Availability and limits

Rate limits and the number of items you can send in one request depend on your plan. See Purge cache: availability and limits. Every change requires explicit confirmation; never repeat an unknown outcome automatically.

Fetch a single zone setting by name Read operation.

Updates a single zone setting by the identifier Every change requires explicit confirmation; never repeat an unknown outcome automatically.

Fetch a list of uploaded Worker scripts. Read operation.

Fetches all rulesets at the zone level. Read operation.

Fetches the latest version of a zone ruleset. Read operation.

Fetches the latest version of the zone entry point ruleset for a given phase. Read operation.

Creates a ruleset at the zone level. Every change requires explicit confirmation; never repeat an unknown outcome automatically.

Updates a zone ruleset, creating a new version. Every change requires explicit confirmation; never repeat an unknown outcome automatically.

Deletes all versions of an existing zone ruleset. Every change requires explicit confirmation; never repeat an unknown outcome automatically.

Fetches Page Rules in a zone. Read operation.

Fetches the details of a Page Rule. Read operation.

Local profile labels/default/auth method only. No provider IDs, credential values or paths. No network.

Complete selected current API input, path and query schema. Local metadata only.

Validate a named operation and return its exact local method/path/query/body/profile. No request, auth validation or provider policy checks.

Read at most five pages of a supported paginated named operation. Provider page metadata determines continuation; missing metadata stops with an explicit unknown continuation.

Local schema-validated DNS batch review capped at 50 actions. Digest binds exact JSON body, zone path and profile label; no account or DNS state read. Not a provider authorization grant.

Verify the reviewed digest and submit one exact native DNS batch with mandatory confirmation. Does not assert remote-state consistency or atomic DNS propagation; no retry.

One parsed GraphQL query only, with variables. No mutations, subscriptions or multiple operations. Permissions, dataset retention, sampling and query limits remain provider controlled.