Verticals

How verticals work

A vertical is the sector an event belongs to, such as healthcare, banking or logistics. Every event carries one in its vertical field.

wede manages the list. Verticals are created and activated by wede. An event with a vertical that is not active in wede returns 422 unknown_vertical.
Your event types are organised by vertical. Your catalog has categories and event types per vertical, pre-loaded by wede for each vertical you operate in, so the same code can exist in two verticals with different meanings. See Events.
Your tenant and zones have their own verticals. The verticals of your tenant are returned in verticals by GET /v1/tenant/me, and each zone lists its verticals_active.
One core for every vertical. Every vertical uses events, delivery through your channel cascade, offline capture and sync, and webhooks. Operational verticals that send people to the field (emergency services, healthcare field teams, field services and delivery) can add the optional teams, dispatch and missions module.

List verticals

GET /v1/verticals is public and needs no credential.

curl https://api.wede.pt/v1/verticals

{
  "data": [
    {
      "code": "healthcare",
      "name": "Healthcare",
      "description": "Emergency medical dispatch, patient monitoring and field medical team coordination",
      "icon": null,
      "is_active": true
    }
  ],
  "count": 1
}

Use the code of an entry with is_active: true in your events. The list grows as wede adds sectors.

Sectors and use cases

The lowercase event types below are examples of codes a tenant creates in its own catalog. The uppercase types are wede categories, which any tenant can use directly.

Healthcare

When hospital or ambulance networks fail, dispatch and clinical alerts must still get through.

Emergency medical dispatch and ambulance coordination
ICU and critical care alerts
Patient status updates between facilities
Field team coordination during mass casualty events
Rural and remote clinic connectivity

{
  "type": "cardiac_arrest",
  "vertical": "healthcare",
  "priority": "critical",
  "idempotency_key": "amb-pt-07-2026-09-26-0001",
  "payload": { "unit": "AMB-PT-07", "eta_minutes": 4 },
  "metadata": { "zone_id": "zone_hospital_lisbon" }
}

Banking and fintech

Payment terminals, ATM networks and field agents often work where connectivity is unreliable.

Payment terminal continuity
ATM network alerts
Field agent coordination
Fraud alert delivery
Mobile banking in low-connectivity areas

{
  "type": "PAYMENT",
  "vertical": "banking",
  "priority": "high",
  "idempotency_key": "atm-ng-042-20260926-0311",
  "payload": { "terminal_id": "ATM-NG-042", "amount": 150000, "currency": "NGN" },
  "metadata": { "zone_id": "zone_atm_network_lagos" }
}

Logistics and delivery

Last-mile delivery, fleets and warehouses keep running in areas with poor coverage.

Delivery confirmation and proof of delivery
Fleet and driver dispatch
Warehouse and cold chain alerts
Port and cross-border coordination

{
  "type": "delivery_confirmed",
  "vertical": "logistics",
  "priority": "normal",
  "idempotency_key": "ord-29841-delivered",
  "payload": { "order_id": "ORD-29841", "driver_id": "DRV-KE-019" },
  "metadata": { "zone_id": "zone_lastmile_nairobi" }
}

Telecommunications

Network operations need to reach field engineers even when the network they maintain is down.

Network operations centre alerts
Field engineer dispatch
Tower and base station faults
Outage management

{
  "type": "site_power_failure",
  "vertical": "telecom",
  "priority": "high",
  "idempotency_key": "bts-ae-112-20260926-001",
  "payload": { "site_id": "BTS-AE-112", "fault_type": "power_failure" },
  "metadata": { "zone_id": "zone_dubai_south" }
}

Emergency services

Civil protection, fire brigades and search and rescue teams work in the hardest connectivity conditions.

Emergency dispatch coordination
Evacuation orders
Incident command and mutual aid
Cross-agency communication

{
  "type": "EMERGENCY",
  "vertical": "emergency",
  "priority": "critical",
  "idempotency_key": "evac-maputo-norte-20260926-001",
  "payload": { "order": "evacuation", "radius_km": 5 },
  "metadata": { "zone_id": "zone_maputo_norte" }
}

Government and public services

Public services and critical infrastructure need continuity by design.

Border control operations
Utility network monitoring (water, electricity, gas)
Civil protection alerts
Infrastructure maintenance dispatch

{
  "type": "STATUS_UPDATE",
  "vertical": "gov",
  "priority": "high",
  "idempotency_key": "grid-ao-07-20260926-overload",
  "payload": { "asset_id": "POWER-GRID-AO-07", "alert_type": "overload" },
  "metadata": { "zone_id": "zone_utility_grid_ao" }
}

Transport

Public transit and rail networks keep coordinating operations when stations or lines lose connectivity.

Rail and transit incident alerts
Maintenance crew dispatch
Service status updates

{
  "type": "STATUS_UPDATE",
  "vertical": "transport",
  "priority": "normal",
  "idempotency_key": "line-2-station-14-20260926-0900",
  "payload": { "line": "2", "station": "14", "status": "delayed" },
  "metadata": { "zone_id": "zone_metro_lisbon" }
}

Examples use the vertical codes healthcare, banking, logistics, telecom, emergency, gov and transport. Always check GET /v1/verticals for the codes active in wede.

Introduction

Core Concepts

Examples by Vertical

How verticals work

List verticals

Sectors and use cases

Healthcare

Banking and fintech

Logistics and delivery

Telecommunications

Emergency services

Government and public services

Transport

​How verticals work

​List verticals

​Sectors and use cases

​Healthcare

​Banking and fintech

​Logistics and delivery

​Telecommunications

​Emergency services

​Government and public services

​Transport

How verticals work

List verticals

Sectors and use cases

Healthcare

Banking and fintech

Logistics and delivery

Telecommunications

Emergency services

Government and public services

Transport