DELETE /v1/domains/{domainId}/disconnect

Autentifikacija

Pošaljite API ključ kao nosivi token. Ključ mora imati dozvolu domains.dns.manage; ključ bez nje se odbija s kodom 403, a ne 404.

Ova krajnja točka ne prihvaća ID organizacije. Vaš ključ već identificira organizaciju kojoj pripada, a odgovor je ograničen na nju.

Isprobajte

Zamijenite sve unutar šiljastih zagrada svojim vlastitim vrijednostima, a rezervirano mjesto za ključ s ključem iz vaše nadzorne ploče.

curl -X DELETE https://api.zinndigital.com/v1/domains/{domainId}/disconnect \
  -H "Authorization: Bearer zdk_live_…"

Prijavljeni ste? API konzola na vašoj nadzornoj ploči automatski unosi stvarni ID vaše organizacije i vaš vlastiti ključ te šalje zahtjev prema aktivnom API-ju kako biste mogli vidjeti stvarni odgovor. Otvori ovu krajnju točku u API konzoli

Pojedinosti

The other half of connectDomain, and not optional: a create with no delete is how an estate fills with dead zones — config nobody serves, still counting against a provider's zone cap and indistinguishable from live config later. Removes the zone at the DNS provider, releases the provider-account placement so the pool stops counting it, then deletes the row and emits domain.disconnected. ⛔ Not domain.deleted (W42-R): that event renders to the customer as a registry release — "it is no longer yours, anyone may now register it" — which is a statement about a registration we held. Stopping DNS hosting for a name somebody else registered is a statement about our service, and the two were one event until 2026-09-09. The zone goes first: if the provider call fails this is a 503 and nothing is changed, because deleting the row first would strand the zone with nothing left pointing at it. A zone already absent at the provider is a success, not an error — otherwise a row could exist that nobody can ever remove. ⛔ Only a connected domain. One registered with us is held at a registrar with a renewal cycle attached, so removing it here would orphan the registration rather than end it — that is the transfer-out/expiry lifecycle. Attempting it is a 409. Requires domains.dns.manage.

Parametri

Pogreške koje ova krajnja točka može vratiti

401 · 403 · 404 · 409 · 429 · 503