Dispatch a team

Dispatch is part of the optional teams, dispatch and missions module, used by operational verticals that send people to the field. Use this endpoint when an operator has already chosen the team. To find the events still waiting for a team, list the dispatch queue with GET /v1/events?undispatched=true: it returns the events without an active mission (no mission, or only missions that ended FAILED). To let wede rank the candidate teams, see Dispatch score and Action dispatch.

POST /v1/teams/dispatch

Authentication

Session token (Authorization: Bearer <token>) with the dispatch:assign permission. Tenant roles with it: company_admin, operational_supervisor, corporate_client.

The integration API key (x-wede-api-key) authenticates as api_user, which has no dispatch:* permission. Calls with an API key return 403 forbidden.

Body

string

required

The event_id wede returned for the event. It must be an existing production event of your tenant, otherwise wede returns 404 event_not_found.

string

required

UUID of the team to dispatch.

string

Up to 500 characters. Stored on the dispatch record and on the mission.

number

Latitude of the incident. Stored on the mission.

number

Longitude of the incident. Stored on the mission.

Example

curl -X POST https://api.wede.pt/v1/teams/dispatch \
  -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",
    "notes": "Use the south entrance",
    "event_lat": 38.7169,
    "event_lng": -9.1395
  }'

Response `201`

The dispatch record.

string

Dispatch record UUID.

string

Your tenant.

string

The event you dispatched to.

string

The dispatched team.

string | null

UUID of the user who dispatched.

string

ISO 8601 timestamp.

string | null

Your notes.

{
  "id": "7d154b16-c8ae-4da7-a949-5a97793c667e",
  "tenant_id": "9c145f7e-83be-4039-8e9c-650796acd3ee",
  "event_id": "fbea1e0d-8f6b-42f5-bf9b-58fe77430f53",
  "team_id": "259edc6e-95f3-42ba-bac5-263cfe51ebc0",
  "dispatched_by": "327739d2-79b6-4e10-8699-a1393e70dbb8",
  "dispatched_at": "2026-06-09T18:42:45.823Z",
  "notes": "Use the south entrance"
}

What happens on dispatch

wede records the dispatch and sets the team status to on_mission.
wede creates a mission for the team with status CREATED and channel_used internet. If the team already has a mission for this event_id, wede keeps that mission and does not create a second one.
wede sends the team.dispatched webhook with { team_id, event_id, notes }.

To send a second team to the same event, dispatch again with the same event_id and the other team_id. Each team gets its own mission. When the mission reaches COMPLETED or FAILED, wede sets the team back to available. The mission outcome never changes the status of the event, which stays its delivery status. If the team does not acknowledge within your acknowledgement timeout, wede substitutes it automatically. See Missions.

Errors

Status	`error`	When
`400`	`validation_error`	The body does not match the schema. `details` lists the failing fields.
`401`	`unauthorized`	Missing, invalid or expired credentials.
`403`	`forbidden`	Your role lacks `dispatch:assign`, or you used an API key.
`404`	`team_not_found`	The `team_id` is not a team of your tenant.
`404`	`event_not_found`	The `event_id` is not an existing production event of your tenant.
`500`	`internal_error`	Unexpected server error.

Dispatch log

GET /v1/teams/dispatch/log

Returns the 100 most recent dispatch records of your tenant, newest first.

Authentication

Session token with the dispatch:view permission. Tenant roles with it: company_admin, operational_supervisor, corporate_client. API keys get 403 forbidden.

Query parameters

string

Return only the dispatch records for this event.

curl "https://api.wede.pt/v1/teams/dispatch/log?event_id=fbea1e0d-8f6b-42f5-bf9b-58fe77430f53" \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN"

Response `200`

{
  "data": [
    {
      "id": "7d154b16-c8ae-4da7-a949-5a97793c667e",
      "tenant_id": "9c145f7e-83be-4039-8e9c-650796acd3ee",
      "event_id": "fbea1e0d-8f6b-42f5-bf9b-58fe77430f53",
      "team_id": "259edc6e-95f3-42ba-bac5-263cfe51ebc0",
      "dispatched_by": "327739d2-79b6-4e10-8699-a1393e70dbb8",
      "dispatched_at": "2026-06-09T18:42:45.823Z",
      "notes": "Use the south entrance",
      "team_name": "Alpha Medical"
    }
  ],
  "count": 1
}

Each record has the dispatch fields above plus team_name.

Errors

Status	`error`	When
`401`	`unauthorized`	Missing, invalid or expired credentials.
`403`	`forbidden`	Your role lacks `dispatch:view`, or you used an API key.
`500`	`internal_error`	Unexpected server error.

SDKs

dispatch in JavaScript and Python.

Overview

Authentication

Events

Teams & Dispatch

Missions

Zones

Billing

Tenant

Webhooks

Sync

Connectivity

Sandbox

Parsers

Onboarding

Dispatch a team

Dispatch a team

Authentication

Body

Example

Response `201`

What happens on dispatch

Errors

Dispatch log

Authentication

Query parameters

Response `200`

Errors

SDKs

​Dispatch a team

​Authentication

​Body

​Example

​Response 201

​What happens on dispatch

​Errors

​Dispatch log

​Authentication

​Query parameters

​Response 200

​Errors

​SDKs

Dispatch a team

Authentication

Body

Example

Response `201`

What happens on dispatch

Errors

Dispatch log

Authentication

Query parameters

Response `200`

Errors

SDKs