Zones

What a zone is

A zone is a geographic operational area: a hospital, a city district, a port, a region or a whole country. Each zone of your tenant has its own connectivity state, and wede uses that state to decide how events for the zone are delivered (see Connectivity). You link an event to a zone with metadata.zone_id set to the zone code. Only zones linked to your tenant are resolved: an event that names another tenant’s zone code is stored without a zone and handled as online.

{
  "type": "cardiac_arrest",
  "vertical": "healthcare",
  "priority": "critical",
  "idempotency_key": "amb07-2026-09-26-0001",
  "payload": { "unit": "AMB-PT-07" },
  "metadata": { "zone_id": "zone_hospital_evora" }
}

Zone fields

Field	Description
`id`	Internal zone ID
`zone_code`	Zone code, used in `metadata.zone_id`, connectivity reports and the zone endpoints
`name`	Name of the zone
`country`	Country code
`region`	Region, or `null`
`lat_center`, `lng_center`	Centre point of the zone
`boundary`	Optional polygon, as an array of `{ "lat", "lng" }` points. In the optional dispatch module, teams whose zone boundary does not contain an event rank lower (see Geofencing)
`verticals_active`	Verticals active in the zone for your tenant
`connectivity_state`	`online`, `degraded`, `sms_only`, `voice_only` or `offline`
`incident_active`	Incident flag of the zone
`last_state_change`	Time of the last state change
`created_at`	Creation time

Who sees which zones

Credential	Zones returned
API key or tenant user session	The zones of your tenant
`country_admin` session	The zones in the countries assigned to that admin

Permissions

Operation	Permission	Who has it
List and read zones	`zones:view`	The integration API key and every tenant role
Create, update and delete zones	`zones:manage`	`company_admin`, `company_tech` and `country_admin` sessions

An API key or another role that tries to create, update or delete a zone receives 403 forbidden.

List zones

GET /v1/tenant/zones

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

{
  "zones": [
    {
      "id": "7e0b2c4a-...",
      "zone_code": "zone_hospital_evora",
      "name": "Hospital Espírito Santo, Évora",
      "country": "PT",
      "region": "Évora",
      "lat_center": "38.568700",
      "lng_center": "-7.903800",
      "boundary": null,
      "created_at": "2026-06-01T09:00:00.000Z",
      "verticals_active": ["healthcare"],
      "connectivity_state": "online",
      "incident_active": false,
      "last_state_change": "2026-09-26T08:00:00.000Z"
    }
  ],
  "total": 1
}

GET /v1/tenant/zones/:zone_code returns one zone, or 404 not_found.

Create a zone

POST /v1/tenant/zones

curl -X POST https://api.wede.pt/v1/tenant/zones \
  -H "Authorization: Bearer <session_token>" \
  -H "Content-Type: application/json" \
  -d '{
    "zone_code": "zone_hospital_evora",
    "name": "Hospital Espírito Santo, Évora",
    "country": "PT",
    "region": "Évora",
    "lat_center": 38.5687,
    "lng_center": -7.9038,
    "verticals_active": ["healthcare"]
  }'

Field	Required	Description
`zone_code`	Yes	Zone code, unique across wede. Use a code specific to your organisation
`name`	Yes	Name of the zone
`country`	Yes	Country code
`region`	No	Region
`lat_center`, `lng_center`	No	Centre point
`verticals_active`	No	Codes of wede verticals

Returns 201 with the zone. Missing required fields return 400 validation_error. A tenant can only create new zones: a zone_code that already exists, whoever it belongs to, returns 409 zone_code_taken. A country_admin can only create zones in its assigned countries (403 forbidden otherwise).

Update a zone

PATCH /v1/tenant/zones/:zone_code accepts name, region, lat_center, lng_center, verticals_active, connectivity_state and boundary, and returns the updated zone. Setting connectivity_state here changes the real state of the zone and sends the same connectivity.degraded and connectivity.restored webhooks as a connectivity report. A change made with a sandbox key only affects the sandbox state. To test state changes without touching the real zone, use a sandbox key with sandbox simulation. A zone can be shared by several tenants. On a shared zone, a tenant can change only its own connectivity_state and verticals_active; changing name, region, lat_center, lng_center or boundary returns 403 shared_zone.

Remove a zone

DELETE /v1/tenant/zones/:zone_code removes the zone from your tenant and returns 204, or 404 not_found.

Zone examples by sector

Sector	Zone code	Area
Healthcare	`zone_hospital_lisbon`	Hospital, Lisbon
Healthcare	`zone_rural_kisumu`	Rural district hospital, Kisumu
Banking	`zone_atm_network_lagos`	ATM network, Lagos
Banking	`zone_field_agents_nairobi`	Field agents, Nairobi
Logistics	`zone_port_luanda`	Port operations, Luanda
Logistics	`zone_lastmile_singapore`	Last-mile delivery, Singapore
Government	`zone_border_control_pt`	Border control, Portugal
Government	`zone_utility_grid_ao`	Utility grid, Angola

Introduction

Core Concepts

Examples by Vertical

What a zone is

Zone fields

Who sees which zones

Permissions

List zones

Create a zone

Update a zone

Remove a zone

Zone examples by sector

​What a zone is

​Zone fields

​Who sees which zones

​Permissions

​List zones

​Create a zone

​Update a zone

​Remove a zone

​Zone examples by sector

What a zone is

Zone fields

Who sees which zones

Permissions

List zones

Create a zone

Update a zone

Remove a zone

Zone examples by sector