zone_code such as zone_lisbon_central. Each zone linked to your tenant carries its own connectivity state, which drives how wede delivers events there.
Authentication
API key or session token with thezones:view permission. The integration API key has it, and so do all tenant roles (company_admin, company_tech, operational_supervisor, field_operator, corporate_client).
- API key:
x-wede-api-key: wede_live_...orwede_test_... - Session token:
Authorization: Bearer <token>
This endpoint returns the real connectivity state of each zone, also for a sandbox key. To read the simulated sandbox state, call
GET /v1/connectivity/status with your sandbox key.Example
Response 200
object[]
Zones linked to your tenant, ordered by name.
string
Zone UUID. This is the value of
zone_id on teams.string
Zone code. Use it in the zone URLs and as
metadata.zone_id on events.string
Display name.
string
ISO 3166-1 alpha-2 country code.
string | null
Region or district.
string | null
Latitude of the zone centre, as a decimal string.
string | null
Longitude of the zone centre, as a decimal string.
object[] | null
Zone outline as a list of
{ lat, lng } points.string
ISO 8601 timestamp.
string[]
Verticals your tenant runs in this zone.
string
online, degraded, sms_only, voice_only or offline.boolean
Whether an incident is flagged in the zone.
string
When the zone settings or connectivity state last changed.
integer
Number of zones returned.
Errors
SDKs
listZones in JavaScript, list_zones in Python.