domains
DELETE /v1/domains/{domainId}/dns/records/{recordId}
Delete a DNS record.
Autentifikacija
Pošaljite API ključ kao bearer token. Ključ mora imati dozvolu domains.dns.manage; ključ bez nje se odbija sa 403, a ne sa 404.
Ovaj krajnji tačka ne prihvata ID organizacije. Vaš ključ već identifikuje organizaciju kojoj pripada, a odgovor je ograničen na nju.
Isprobajte
Zamenite bilo šta u uglastim zagradama sopstvenim vrednostima, a ključni placeholder sa ključem sa vaše kontrolne table.
curl -X DELETE https://api.zinndigital.com/v1/domains/{domainId}/dns/records/{recordId} \
-H "Authorization: Bearer zdk_live_…"Prijavljeni ste? API konzola na vašoj kontrolnoj tabli automatski popunjava ID vaše stvarne organizacije i vaš sopstveni ključ, i izvršava zahtev nad API-jem uživo tako da možete videti stvarni odgovor. Otvorite ovu krajnju tačku u API konzoli
Detalji
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.
Parametri
| Naziv | Vrsta | Obavezno | Šta je ovo |
|---|---|---|---|
domainId (path) | Uuid | Da | The domain's id. |
recordId (path) | string | Da | The DNS record's provider id. |
confirm_mail_change (query) | boolean | Ne | 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… |
Greške koje ovaj krajnji tačka može da vrati
401 · 403 · 404 · 409 · 429 · 502 · 503