Create DNS record with the Cloudflare API

Creates a DNS record in a zone and returns it, with its id. A and AAAA records cannot share a name with a CNAME, and an NS record cannot share a name with any other record.

Identifier
cloudflare_create_dns_record

The request

POST https://connect.reportei.com/api/tools/cloudflare_create_dns_record/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>",
    "type": "A",
    "name": "<name>"
  }
}

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.
typestringYesRecord type.Values: A, AAAA, CNAME, MX, TXT, NS, CAA, SRV, HTTPS
namestringYesFull name of the record, including the zone, such as www.example.com; the zone itself for the root.
contentstringNoValue of the record: the IPv4 or IPv6 address, the target host of a CNAME, MX or NS, or the text of a TXT. CAA and SRV records use data instead.
ttlnumberNoTime to live in seconds, from 60 to 86400, or 1 for automatic (the default).
proxiedbooleanNoSends the traffic through Cloudflare. Only for A, AAAA and CNAME records. The default is false.
prioritynumberNoRequired for MX records. Lower values are preferred.
commentstringNoNote about the record, with no effect on DNS answers.
dataobjectNoParts of a CAA or SRV record: flags, tag and value for CAA, such as {flags: 0, tag: issue, value: letsencrypt.org}; priority, weight, port and target for SRV.

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