GET /v1/hosting/locations

Autenticación

Envía una clave de API como token de portador. Este endpoint no especifica un permiso concreto en la especificación, así que otorga a tu clave los mínimos privilegios necesarios y comprueba la respuesta en lugar de dar por sentado.

Este endpoint no requiere ningún id de organización. Su clave ya identifica la organización a la que pertenece, y la respuesta está delimitada a ella.

Pruébalo

Reemplaza cualquier elemento entre corchetes angulares por tus propios valores, y el marcador de posición key con una clave de tu panel de control.

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

¿Has iniciado sesión? La consola de la API en tu panel de control rellena el ID de tu organización real y tu propia clave, y ejecuta la solicitud contra la API en vivo para que puedas ver la respuesta real. Abre este endpoint en la consola de la API

Detalles

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.

Parámetros

Respuesta

Errores que este endpoint puede devolver

401 · 429