Skip to main content
Once a domain has a DNS zone, created during purchase or with setup-dns, you can manage its records directly through the API.
Listing records accepts either an API key or a bearer token. Creating, reading a single record, updating, deleting, and syncing currently accept an API key only. See Authentication for the full breakdown.

List existing records

Results are paginated with skip and limit query parameters (default limit is 100):

Create a record

Point your domain at a server by creating an A record. record_type accepts A, AAAA, CNAME, MX, TXT, NS, SRV, or CAA.
For subdomains, include the full hostname in name, for example, api.acmewidgets.com. For an MX record, also set priority; for a Cloudflare-hosted zone, set proxied: true to route traffic through Cloudflare’s proxy.

Update a record

Send only the fields you want to change, PUT here behaves as a partial update, so omitted fields keep their current value.

Delete a record

A successful delete returns 204 No Content.

Sync records from the provider

If records were changed directly in your DNS provider’s dashboard (for example, in Cloudflare) rather than through this API, sync them back into Dotlet so future API calls reflect the current state.
Run a sync before scripting bulk updates, so you’re not overwriting changes the API doesn’t know about yet.

Next steps

DNS API reference

Full parameter and response details for every DNS endpoint.