domains
DELETE /v1/domains/{domainId}/dns/records/{recordId}
Delete a DNS record.
Authentication
Send an API key as a bearer token. The key must carry the domains.dns.manage permission; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X DELETE https://api.zinndigital.com/v1/domains/{domainId}/dns/records/{recordId} \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Removes the record `recordId` from the domain's hosted zone. Requires `domains.dns.manage`. As for update, a record hidden from the caller's line 404s rather than confirming it exists. **Deleting an apex `MX` is refused** `409 MAIL_CHANGE_REFUSED` unless `confirm_mail_change=true` (issue #622). It fires on *any* apex MX deletion, not only the last one — "delete every MX one at a time" is the failure mode, and by the time the last one goes three deletions have already happened. The message says whether the domain would stop receiving mail entirely or merely fall back to a remaining host.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
domainId (path) | Uuid | Yes | The domain's id. |
recordId (path) | string | Yes | The DNS record's provider id. |
confirm_mail_change (query) | boolean | No | Set `true` to proceed with a record change that would move or remove this domain's inbound email (issue #622). Without it, a write that stops mail reaching a host it reaches tod… |
Errors this endpoint can return
401 · 403 · 404 · 409 · 429 · 502 · 503