hosting
DELETE /v1/sites/{siteId}/edge-domains/{hostname}
Stop serving this hostname from the deploy target.
Tabbatar da Asali
Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin hosting.deploy.manage; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.
Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.
Gwada
May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.
curl -X DELETE https://api.zinndigital.com/v1/sites/{siteId}/edge-domains/{hostname} \
-H "Authorization: Bearer zdk_live_…"An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API
Bayani
Detaches the hostname at the provider and forgets it here. The DNS records are deliberately left in place: they are in the customer's zone, and a name that has stopped serving is a fixable state while a record we silently deleted is not. Requires `hosting.deploy.manage`.
Sigogi
| Suna | Nau'i | Ana buƙata | Abin da yake |
|---|---|---|---|
siteId (path) | Uuid | Eh | Site ID (UUIDv7). |
hostname (path) | string | Eh | The bound hostname, lower-cased and without a trailing dot. |
Kuskuren da wannan matsaya za ta iya maido wa
401 · 403 · 404 · 422 · 429