GET /v1/hosting/locations

Tabbatar da Asali

Aiko da maɓallin API a matsayin bearer token. Wannan ma'anar ba ta bayyana takamaiman izini ba a cikin ƙayyadaddun bayanai, don haka ba wa maɓallin ku mafi ƙarancin abin da yake buƙata kuma ku bincika amsar maimakon yin zato.

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/hosting/locations \
  -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 data centre a new site may be placed in, across **both** estates (docs/370): the locations this platform has activated for the managed hosting range (docs/62 §3.5), plus the regions of our own fleet that currently have a worker able to take the site. Activating a managed-range location is a reseller-level purchase — activate once, host unlimited sites in it — and a fleet region is available whenever a box there is active, accepting deploys and not full. The answer carries no tenant scope; it is authenticated only because it describes our estate rather than being marketing copy. An empty list is a real answer, not an error: nothing is activated and no fleet worker can take the site, a managed-range location could not be pinned with the configuration present, or the line is one we do not offer a choice on. The client must then hide the picker and let the default placement apply — it must never substitute a list of its own, because creating a site in a location we have not activated is refused by the vendor after the customer has chosen, and a fleet region with no box behind it fails in placement for the same reason. `code` is the placement identifier (`lhr`, `nbg1`) and the suffix of the i18n key the client renders; `country` is ISO-3166 alpha-2 for a decorative flag. There is deliberately **no display name** — location names are translated like every other user-facing string, and a flag is never the accessible name.

Sigogi

Martani

Kuskuren da wannan matsaya za ta iya maido wa

401 · 429