DELETE /v1/domains/{domainId}/disconnect

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}/disconnect \
  -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

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.deleted`. **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

Greške koje ovaj krajnji tačka može da vrati

401 · 403 · 404 · 409 · 429 · 503