List DNS records with the Cloudflare API

Lists the DNS records of a zone, with id, type, name, content, proxied, ttl and comment. Filters work together unless match is any. Paginate with page and per_page; result_info.total_pages tells how many pages there are.

Identifier
cloudflare_list_dns_records

The request

POST https://connect.reportei.com/api/tools/cloudflare_list_dns_records/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "zone_id": "<zone_id>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
zone_idstringYesThe id of the zone, from List zones.
typestringNoOnly records of this type.Values: A, AAAA, CAA, CERT, CNAME, DNSKEY, DS, HTTPS, LOC, MX, NAPTR, NS, OPENPGPKEY, PTR, SMIMEA, SRV, SSHFP, SVCB, TLSA, TXT, URI
namestringNoExact full name of the record, including the zone, such as www.example.com.
contentstringNoExact content of the record, such as an IP address.
commentstringNoExact comment of the record.
proxiedbooleanNoOnly records that go, or do not go, through the Cloudflare proxy.
matchstringNoall requires every filter (the default); any accepts records that pass at least one.Values: all, any
orderstringNoSort field. The default is type.Values: type, name, content, ttl, proxied
directionstringNoSort order. The default is asc.Values: asc, desc
per_pagenumberNoRecords per page. The default is 100.
pagenumberNoPage number, starting at 1.

Supported connections

Your customer connects their Cloudflare account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/cloudflare_list_dns_records. It becomes your agent's tool definition with no conversion.

Other Cloudflare tools

See all 8 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.