Missions

Missions belong to the optional teams, dispatch and missions module, used by operational verticals that send people to the field. A mission is one team’s assignment to one event. wede creates it when you dispatch a team or when automatic dispatch picks a team. Your apps then move it through its statuses and attach field feedback.

Authentication

All mission endpoints need a session token (Authorization: Bearer <token>).

Operation	Permission	Tenant roles with it
List and read missions	`missions:view`	`company_admin`, `company_tech`, `operational_supervisor`, `corporate_client`
List the missions of your own teams (`GET /v1/missions/my`)	`missions:receive`	`field_operator`
Create a mission	`missions:manage`	`company_admin`, `company_tech`, `operational_supervisor`
Update mission status	`missions:manage` or `missions:receive`	`company_admin`, `company_tech`, `operational_supervisor`, `field_operator` (only missions of a team the user is a member of)

The integration API key (x-wede-api-key) has no missions:* permission. Calls with an API key return 403 forbidden. Subscribe to the mission.created and mission.status_updated webhooks to follow missions from your server.

Mission statuses

Status	Meaning
`CREATED`	The mission exists. Every mission starts here.
`SENT`	The mission reached the team.
`ACK`	The team acknowledged the mission.
`ON_ROUTE`	The team is travelling to the incident.
`ON_SITE`	The team is at the incident.
`COMPLETED`	The response ended successfully.
`FAILED`	The response could not be completed.

Your apps set every status after CREATED with Update mission status. wede records each status with its timestamp and enforces the lifecycle:

A mission only moves forward in the order above. It can skip steps, for example from SENT straight to ON_SITE.
FAILED can be set from any status that is not final.
COMPLETED and FAILED are final: a mission in either status cannot change again.
Any other change returns 409 invalid_transition.

When a mission reaches COMPLETED or FAILED, wede sets the team back to available. The mission outcome never changes the status of the event, which is always its delivery status (see Events).

Substitution when a team does not acknowledge

Your tenant has an acknowledgement timeout, reinforcement_timeout_min in the dispatch settings (set to 0 to turn substitution off). If a mission is still CREATED or SENT when the timeout passes, wede substitutes the team:

The mission is set to FAILED with "feedback": { "reason": "no_acknowledgement" }, and its team becomes available again. You receive mission.status_updated.
wede ranks the free teams that have not yet been called for this event and dispatches the best one. This creates a new mission and sends team.dispatched with substitution: true, mission_id, replaced_team_id and replaced_mission_id.
If no team is free, the event goes back to the dispatch queue (GET /v1/events?undispatched=true) so a dispatcher can handle it.

The replaced team is never called again for the same event, so each substitution moves to a new team.

The mission object

string

Mission UUID.

string

Your tenant.

string

Event the mission responds to.

string

Assigned team.

string | null

Dispatch record that created the mission.

string | null

UUID of the team member in charge.

string

Current status.

string

Channel recorded for reaching the team: internet, sms or voice.

string | null

Vertical of the mission.

string | null

Priority label.

object | null

Operational data for the team. When wede creates the mission (dispatch, automatic dispatch, substitution), this is a snapshot of the event fields marked Show to team in the parser the event was written with, keyed by field name with the field codes as values. Fields the organisation did not mark for the team, and keys outside the parser, are never copied. The snapshot is cleared when the mission ends (COMPLETED, FAILED, REFUSED, SUBSTITUTED, STOOD_DOWN).

object

Labels of the payload fields, keyed by field name: { "label": "Incident type", "value_label": "Cardiac arrest" }. value_label is present for enumerated fields. Absent when the event has no parser. Returned by GET /v1/missions/my and GET /v1/missions/{id}.

array

Every team called to the same event, so a team knows who else is involved and where they stand: { mission_id, team_id, team_name, role, status, dispatched_at, updated_at, channel_used }. role is primary or reinforcement. Never includes team members. Returned by GET /v1/missions/my and GET /v1/missions/{id}.

object | null

Latest feedback sent with a status update.

string | null

Notes for the team.

number | null

Incident latitude.

number | null

Incident longitude.

string

When the mission was created.

string | null

When the mission last received each status.

string

ISO 8601 timestamp.

string

ISO 8601 timestamp.

List missions

GET /v1/missions

Returns missions of your tenant, most recently dispatched first.

string

One of the mission statuses.

string

Only missions of this team.

string

Only missions assigned to this team member.

integer

default:"50"

Maximum number of missions, from 1 to 200.

curl "https://api.wede.pt/v1/missions?status=ON_ROUTE&limit=20" \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN"

Response 200

{
  "data": [
    {
      "id": "a3f0c2d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
      "tenant_id": "9c145f7e-83be-4039-8e9c-650796acd3ee",
      "event_id": "fbea1e0d-8f6b-42f5-bf9b-58fe77430f53",
      "team_id": "259edc6e-95f3-42ba-bac5-263cfe51ebc0",
      "dispatch_id": "7d154b16-c8ae-4da7-a949-5a97793c667e",
      "assigned_member": null,
      "status": "ON_ROUTE",
      "channel_used": "internet",
      "vertical": "healthcare",
      "priority": null,
      "payload": null,
      "feedback": null,
      "notes": "Use the south entrance",
      "event_lat": 38.7169,
      "event_lng": -9.1395,
      "dispatched_at": "2026-06-09T18:42:45.823Z",
      "sent_at": "2026-06-09T18:42:50.000Z",
      "ack_at": "2026-06-09T18:43:30.000Z",
      "on_route_at": "2026-06-09T18:44:00.000Z",
      "on_site_at": null,
      "completed_at": null,
      "failed_at": null,
      "created_at": "2026-06-09T18:42:45.823Z",
      "updated_at": "2026-06-09T18:44:00.000Z"
    }
  ],
  "count": 1
}

List my missions

GET /v1/missions/my

For field apps. Returns the missions of every team the signed-in user is a member of, most recently dispatched first, up to 50. Each mission includes parser_schema, labels and event_teams, as in Get a mission. The response is { data, count }. Needs missions:receive (field_operator). This is what a field team works from: payload holds the values of the fields marked Show to team, labels their human labels, parser_schema the field definitions, and event_teams the other teams on the same event with their current state. A field operator reading the event itself (GET /v1/events/{id}) sees the same reduced payload; see Get an event.

curl https://api.wede.pt/v1/missions/my \
  -H "Authorization: Bearer FIELD_USER_SESSION_TOKEN"

Get a mission

GET /v1/missions/{id}

Returns the mission object plus parser_schema (the fields marked Show to team of the parser the event was written with, or of the active model of its vertical whose type field maps to the event type; an empty array when there is none), labels and event_teams. Your field app can use parser_schema to build the feedback form.

curl https://api.wede.pt/v1/missions/a3f0c2d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN"

Create a mission

POST /v1/missions

Creates a mission without a dispatch. It does not change the team’s status and does not record a dispatch: to send a team, use Dispatch a team.

string

required

Event identifier, at least 1 character.

string

required

Team UUID.

string

UUID of a dispatch record.

string

UUID of the team member in charge.

string

default:"internet"

internet, sms or voice.

string

Vertical code.

string

Priority label.

object

Operational data for the team.

string

Up to 1000 characters.

number

Incident latitude.

number

Incident longitude.

curl -X POST https://api.wede.pt/v1/missions \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "event_id": "fbea1e0d-8f6b-42f5-bf9b-58fe77430f53",
    "team_id": "259edc6e-95f3-42ba-bac5-263cfe51ebc0",
    "vertical": "healthcare",
    "event_lat": 38.7169,
    "event_lng": -9.1395
  }'

team_id must be a team of your tenant, otherwise wede returns 404 team_not_found. Returns 201 with the mission object. If the team already has a mission for this event_id, wede returns that mission with "already_existed": true instead of creating a second one. wede sends the mission.created webhook with { mission_id, event_id, team_id, status: "CREATED" }.

Update mission status

PATCH /v1/missions/{id}/status

string

required

Mission UUID.

string

required

One of the mission statuses.

object

Structured feedback from the field, for example the fields of your parser. Replaces the stored feedback.

curl -X PATCH https://api.wede.pt/v1/missions/a3f0c2d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d/status \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "status": "COMPLETED",
    "feedback": { "patient_condition": "stable" }
  }'

Returns 200 with the updated mission object. wede sends the mission.status_updated webhook with { mission_id, status, feedback }. A user who only has missions:receive (field_operator) can update only missions of a team they are a member of; any other mission returns 403 forbidden. A change that breaks the lifecycle returns 409 invalid_transition.

Errors

Status	`error`	When
`400`	`validation_error`	Invalid body, or a `status` filter that is not a mission status.
`401`	`unauthorized`	Missing, invalid or expired credentials.
`403`	`forbidden`	Your role lacks the permission, you used an API key, or a `field_operator` updated a mission of a team they are not a member of.
`404`	`not_found`	No mission with this `id` in your tenant (get, update).
`404`	`team_not_found`	The `team_id` is not a team of your tenant (create).
`409`	`invalid_transition`	The status change breaks the mission lifecycle (update).
`500`	`internal_error`	Unexpected server error.

SDKs

listMissions, getMission and updateMissionStatus in JavaScript; list_missions, get_mission and update_mission_status in Python.

Overview

Authentication

Events

Teams & Dispatch

Zones

Billing

Tenant

Webhooks

Sync

Policies

Connectivity

Sandbox

Parsers

Onboarding

Missions

Authentication

Mission statuses

Substitution when a team does not acknowledge

The mission object

List missions

List my missions

Get a mission

Create a mission

Update mission status

Errors

SDKs

​Authentication

​Mission statuses

​Substitution when a team does not acknowledge

​The mission object

​List missions

​List my missions

​Get a mission

​Create a mission

​Update mission status

​Errors

​SDKs

Authentication

Mission statuses

Substitution when a team does not acknowledge

The mission object

List missions

List my missions

Get a mission

Create a mission

Update mission status

Errors

SDKs