GET /v1/hosting/locations

Autentifikacija

Pošaljite API ključ kao bearer token. Ova krajnja tačka ne navodi specifičnu dozvolu u specifikaciji, zato dodelite svom ključu minimum potrebnih ovlašćenja i proverite odgovor umesto da pretpostavljate.

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 GET https://api.zinndigital.com/v1/hosting/locations \
  -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

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.

Parametri

Odgovor

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

401 · 429