GET /v1/hosting/locations

Authentication

Send an API key as a bearer token. This endpoint checks no specific permission, so any key for your organisation can call it.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/hosting/locations \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Every data centre a new site may be placed in: the regions of our own fleet that currently have a worker able to take the site — active, accepting deploys, not full, serving the line, in the pool its sites are placed in. ⚖️ Owner ruling 2026-09-22: only regions with real fleet capacity are offered, so the managed-range (resold) locations this endpoint also returned until then are no longer offered. The same list, with city and name key, is listHostingRegions. 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.

Parameters

Response

Errors this endpoint can return

401 · 429