Get a zone

GET /v1/tenant/zones/{zone_code}

Authentication

API key or session token with the zones: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_... or wede_test_...
Session token: Authorization: Bearer <token>

Path parameters

string

required

Code of a zone linked to your tenant, for example zone_lisbon_central.

Example

curl https://api.wede.pt/v1/tenant/zones/zone_lisbon_central \
  -H "x-wede-api-key: wede_live_YOUR_KEY"

Response `200`

The zone object, with the same fields as in List zones.

{
  "id": "4f1c2a0e-6b1d-4a57-9d0e-2f1b7c3d8e21",
  "zone_code": "zone_lisbon_central",
  "name": "Lisboa Central",
  "country": "PT",
  "region": "Lisboa",
  "lat_center": "38.716900",
  "lng_center": "-9.139900",
  "boundary": null,
  "created_at": "2026-05-01T10:00:00.000Z",
  "verticals_active": ["healthcare"],
  "connectivity_state": "online",
  "incident_active": false,
  "last_state_change": "2026-06-09T17:00:00.000Z"
}

connectivity_state is the real state of the zone, also for a sandbox key.

Errors

Status	`error`	When
`401`	`unauthorized`	Missing, invalid or revoked credentials.
`403`	`forbidden`	The credential lacks `zones:view`.
`404`	`not_found`	No zone with this code is linked to your tenant.
`500`	`internal_error`	Unexpected server error.

SDKs

getZone in JavaScript, get_zone in Python.

Overview

Authentication

Events

Teams & Dispatch

Missions

Zones

Billing

Tenant

Webhooks

Sync

Policies

Connectivity

Sandbox

Parsers

Onboarding

Authentication

Path parameters

Example

Response `200`

Errors

SDKs

​Authentication

​Path parameters

​Example

​Response 200

​Errors

​SDKs

Authentication

Path parameters

Example

Response `200`

Errors

SDKs