Connectivity

Connectivity per zone

Each of your zones has its own connectivity state. Your devices and systems report it to wede, and wede uses it to decide how events for that zone are delivered. Events carry their zone in metadata.zone_id; an event without a zone is handled as online.

Connectivity states

State	Meaning	How wede delivers events for the zone
`online`	Internet available	REST (`rest_full`)
`degraded`	Internet available with reduced quality	REST: `rest_compressed` for `high` and `critical` events, `rest_full` for the others
`sms_only`	No internet, SMS available	Continuity mode of your tenant
`voice_only`	No internet, voice available	Continuity mode of your tenant
`offline`	No external connectivity	Continuity mode of your tenant

Continuity modes

Each tenant runs in one of two continuity modes, set by its plan. Automatic cascade. For a zone that is not online or degraded, wede tries the fallback channels of your tenant (SMS, voice, satellite, LoRa, edge) in the order agreed for your tenant. Each channel is retried before wede moves to the next, and critical events get more attempts per channel. The first channel that delivers is recorded in channel_used. If the whole cascade fails, the event is not marked as failed: it is queued for store-and-forward. Store-and-forward. Events are queued (channel_used: "queued_offline") and completed when the queued operation is reconciled after connectivity returns. No intermediate channels are attempted. In both modes, each queued operation has a unique identity and is accepted once: the same operation can never be completed twice. The channel used for each event is on the event (channel_used) and in the delivery webhooks. See Events.

Report connectivity

POST /v1/connectivity/report

curl -X POST https://api.wede.pt/v1/connectivity/report \
  -H "x-wede-api-key: wede_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "zone_id": "zone_hospital_evora",
    "state": "degraded",
    "detected_at": "2026-09-26T10:14:00Z",
    "signal_strength_dbm": -85,
    "network_type": "lte",
    "device_id": "3f1c9a52-7d7e-4a51-9f0e-2b8c6e1d4a10"
  }'

Field	Required	Description
`zone_id`	Yes	Code of one of your zones
`state`	Yes	`online`, `degraded`, `sms_only`, `voice_only` or `offline`
`detected_at`	Yes	ISO 8601 time the state was detected
`signal_strength_dbm`	No	Integer, or `null`
`network_type`	No	`wifi`, `lte`, `umts`, `edge`, `gprs`, `gsm`, `none`, or `null`
`device_id`	No	The device that detected the state

A successful report returns 204 and sets the zone’s state. An invalid body returns 400 invalid_payload; a zone code that is not linked to your tenant returns 422 invalid_reference. API keys and sessions whose role includes connectivity reporting (including field_operator) can report. The wede SDKs can send these reports for you.

Read connectivity status

GET /v1/connectivity/status, optionally with ?zone_id=<zone code>.

{
  "zones": [
    {
      "zone_id": "zone_hospital_evora",
      "zone_name": "Hospital Espírito Santo, Évora",
      "country": "PT",
      "state": "degraded",
      "incident_active": false,
      "last_updated": "2026-09-26T10:14:02.000Z",
      "fallback_channel": "rest_degraded"
    }
  ],
  "as_of": "2026-09-26T10:15:00.000Z"
}

Field	Description
`zone_id`	Zone code
`zone_name`	Zone name
`country`	Country code of the zone
`state`	Current connectivity state
`incident_active`	Incident flag of the zone
`last_updated`	Last state change
`fallback_channel`	Channel associated with the state: `rest_full` (online), `rest_degraded` (degraded), `sms` (sms_only), `voice` (voice_only) or `offline`

fallback_channel summarises the state. The channel that actually delivers an event depends on your continuity mode and cascade, and is recorded on each event.

Webhooks

wede sends two connectivity webhooks:

connectivity.degraded when a zone leaves online;
connectivity.restored when a zone returns to online.

Changes between two states that are not online (for example degraded to offline) do not send a webhook.

{
  "id": "d0c5e3a2-...",
  "event": "connectivity.degraded",
  "created_at": "2026-09-26T10:14:02.000Z",
  "tenant_id": "b2c4...",
  "environment": "production",
  "data": {
    "zone_id": "zone_hospital_evora",
    "previous_state": "online",
    "state": "sms_only",
    "detected_at": "2026-09-26T10:14:00Z"
  }
}

Subscribe with POST /v1/webhooks. See Webhooks for signatures and retries.

Sandbox simulation

With a sandbox key (wede_test_), you can simulate a connectivity state for one of your zones and see how your integration reacts:

curl -X POST https://api.wede.pt/v1/sandbox/simulate-connectivity \
  -H "x-wede-api-key: wede_test_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "zone_id": "zone_hospital_evora", "connectivity_state": "sms_only", "duration_seconds": 300 }'

Field	Required	Description
`zone_id`	Yes	Code of one of your zones, else `422 invalid_reference`
`connectivity_state`	Yes	`online`, `degraded`, `sms_only`, `voice_only` or `offline`
`duration_seconds`	No	5 to 3600, default 60

Response 200:

{
  "zone_id": "zone_hospital_evora",
  "environment": "sandbox",
  "state_applied": "sms_only",
  "active_until": "2026-09-26T10:20:00.000Z"
}

The simulation changes only the sandbox state of the zone, never its real state or production traffic. A production key receives 403 sandbox_key_required. With a sandbox key:

GET /v1/connectivity/status shows the sandbox state of each zone (online unless a simulation is active);
POST /v1/connectivity/report changes only the sandbox state;
sandbox events follow the simulated state, and connectivity webhooks are sent with "environment": "sandbox".

Introduction

Core Concepts

Examples by Vertical

Connectivity per zone

Connectivity states

Continuity modes

Report connectivity

Read connectivity status

Webhooks

Sandbox simulation

​Connectivity per zone

​Connectivity states

​Continuity modes

​Report connectivity

​Read connectivity status

​Webhooks

​Sandbox simulation

Connectivity per zone

Connectivity states

Continuity modes

Report connectivity

Read connectivity status

Webhooks

Sandbox simulation