Create event

POST /v1/events

Accepts an event and returns 202 Accepted at once. wede then delivers it in the background according to your continuity mode, the connectivity of the event’s zone and your channel cascade. Follow the outcome with webhooks or GET /v1/events/:event_id.

Authentication

API key or session token with the events:write permission. API keys have it. The event is stored in the environment of the credential: sandbox for wede_test_ keys, production for wede_live_ keys and session tokens.

Request body

string

required

Event type: an active type of your catalog for this vertical, lowercase codes such as cardiac_arrest (see GET /v1/catalog). Otherwise the request fails with 422 unknown_event_type, and known_types lists accepted codes.

string

required

Vertical of the operation, for example healthcare. Must be a vertical active in wede, otherwise 422 unknown_vertical.

string

One of low, normal, high, critical. Without it, the default priority of the event type applies (normal when the type has none).

string

required

1 to 128 characters. Identifies the operation. The same key again in the same environment returns 409 duplicate_event. See Idempotency.

object

required

Your operation data, any JSON object. wede delivers it and clears the stored copy once a channel confirms delivery.

object

Optional context about where and how the event was produced.

Show properties

string

Code of the zone where the operation happened (for example zone_lisbon_central). wede uses the connectivity of this zone to choose the delivery path. Only zones linked to your organisation are resolved: a code that is not yours is ignored and the event is stored without a zone. Without a zone, the event is treated as online.

object

Where the operation happened: lat (from -90 to 90) and lng (from -180 to 180).

string

Your identifier for the operator or device user.

string

Version of the client that produced the event.

string

ISO 8601 date-time when the operation was captured, if it was captured offline.

string

Connectivity at capture time: online, degraded, sms_only, voice_only or offline.

object

Optional one-off recipient for this event, used for this delivery only. When the delivery goes through the fallback channels, wede keeps it encrypted with your organisation’s key while the delivery runs and removes it when it ends. It is never kept with the event.

Show properties

string

Phone number to reach by SMS or voice. When omitted, wede uses the recipients configured for your tenant.

string

Identifier of the satellite or LoRa device to reach. Satellite and LoRa delivery address a device by this identifier.

Unknown top-level fields are ignored.

Example

curl -X POST https://api.wede.pt/v1/events \
  -H "x-wede-api-key: wede_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "cardiac_arrest",
    "vertical": "healthcare",
    "priority": "critical",
    "idempotency_key": "incident-2026-09-26-0042",
    "payload": { "patient_ref": "PT-001", "location": "Rua Augusta 10" },
    "metadata": { "zone_id": "zone_lisbon_central" }
  }'

Response

202 Accepted

{
  "event_id": "0ee3dfbe-6a0b-4c55-9d0e-2b7f3f1c9a40",
  "idempotency_key": "incident-2026-09-26-0042",
  "status": "pending",
  "environment": "production",
  "channel_selected": "rest_full",
  "request_id": "req-1a"
}

string

Event ID (UUID).

string

The key you sent.

string

Always pending at this point.

string

production or sandbox.

string

How the event reached wede. Always rest_full for events submitted to this endpoint. The channel used to deliver the event is channel_used, returned by GET /v1/events/:event_id and sent in the event.delivered webhook.

string

Request identifier.

The response also contains estimated_delivery_ms. Do not rely on it: it is not a measurement of the delivery.

object

What the optional teams module will do with this event: status is queued (automatic dispatch), manual (an operator decides), not_dispatchable with reason: type_does_not_require_teams (the type sends nobody), off (no teams module) or sandbox.

What happens next

wede emits event.created to your webhooks.
wede picks the delivery path:
- In store-and-forward mode, the event is queued for delivery when connectivity returns (channel_used: "queued_offline").
- When the zone is online or degraded, the event is delivered over the internet path and becomes completed: rest_full, or rest_compressed for high and critical events in a degraded zone.
- When the zone is sms_only, voice_only or offline, wede follows your channel cascade (SMS, voice, satellite, LoRa, edge) in the order you configured. The first channel that delivers makes the event completed. If no channel in the cascade delivers, the event stays pending and is queued (queued_offline) rather than dropped.
wede emits event.delivered (status completed), event.failed or event.status_changed (queued, status pending) with the result. See Webhook events.
Once the event is completed, wede clears its stored payload.

In sandbox the same decision runs against the simulated state of the zone, no message leaves wede, and a simulated delivery also ends completed.

Errors

Status	Code	When
400	`invalid_payload`	The body is not valid JSON
401	`unauthorized`	Credential missing, malformed, revoked or expired
403	`forbidden`	The credential lacks `events:write`
409	`duplicate_event`	An event with this `idempotency_key` already exists in this environment
422	`invalid_payload`	A field is missing or invalid. `details` lists each problem
422	`unknown_vertical`	`vertical` is not registered or not active
422	`unknown_event_type`	`type` is not an active type of your catalog for this vertical. `known_types` lists accepted codes
503	`service_unavailable`	The API key could not be validated right now. Retry

{
  "error": "invalid_payload",
  "message": "...",
  "details": [
    { "code": "invalid_enum_value", "path": ["priority"], "message": "Invalid enum value. Expected 'low' | 'normal' | 'high' | 'critical', received 'urgent'" }
  ],
  "request_id": "req-1b",
  "docs_url": "https://docs.wede.pt/events"
}

Overview

Authentication

Events

Teams & Dispatch

Missions

Zones

Billing

Tenant

Webhooks

Sync

Connectivity

Sandbox

Parsers

Onboarding

Authentication

Request body

Example

Response

What happens next

Errors

​Authentication

​Request body

​Example

​Response

​What happens next

​Errors

Authentication

Request body

Example

Response

What happens next

Errors