GET /v1/hosting/locations

Xaqiijinta aqoonsiga

U dir fure API ahaan calaamad muujisa (bearer token). Barta dhammaadka ee kani ma caysino luqad ahaan oggolaansho gaar ah oo ku dhex jirta qeexidda, markaa sii furahaaga inta ugu yar ee uu u baahan yahay oo fiiri jawaabta halka aad wax ka qaadan lahayd.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

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

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Faahfaahin

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.

Cabiraha

Jawaab

Cilladaha ay bartaani soo celin karto

401 · 429