hosting

GET /v1/sites/{siteId}/edge-domains

The custom domains bound to this site's deploy target.

Dukkan hosting wuraren ƙarshe

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin sites.view; 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 GET https://api.zinndigital.com/v1/sites/{siteId}/edge-domains \
  -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

Every hostname the site serves at its edge host, with the exact DNS records it needs, which of the three DNS tiers it landed on, and when we last saw those records actually resolve from a public resolver. A site with no edge-host project returns an empty list rather than a 404 — that is an ordinary state (every fleet site is in it) and the dashboard renders it as the add-a-domain form. Requires `sites.view`.

Sigogi

SunaNau'iAna buƙataAbin da yake
siteId (path)UuidEhSite ID (UUIDv7).

Martani

SunaNau'iAna buƙataAbin da yake
dataSiteCustomDomain[]Eh

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 404 · 429