GET /v1/sites/{siteId}/subdomains

Uthibitishaji

Tuma ufunguo wa API kama tokeni ya kubeba. Ufunguo lazima uwe na ruhusa ya sites.view; ufunguo usio nayo unakataliwa kwa 403, si 404.

Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.

Jaribu

Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/subdomains \
  -H "Authorization: Bearer zdk_live_…"

Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API

Maelezo

The subdomains served by the site's hosting package and the document root each one points at. ⛔ Subdomains are the only surface here with a real **quantity** ceiling: `limit` is the lower of what the package template permits and what the customer bought, so `can_create` is arithmetic and not merely `permitted`. ⚖️ **On our own fleet the ceiling is the plan's `max_sites`, because a subdomain spends one of them** (owner ruling 2026-09-01). `limit` is then the site cap and `used` carries how much of it is already spent — by the customer's **sites as well as their subdomains** — so a client must render the caption from `used` and not from `data.length`. On the resold line `used` is absent and counting the rows is correct; nothing else about the shape differs. Requires `sites.view`. `404` for a site with no managed hosting package and no own-fleet placement.

Vigezo

Majibu

Hitilafu ambazo mwisho huu unaweza kurudisha

401 · 403 · 404 · 429 · 503