Teams

Teams belong to the optional teams, dispatch and missions module, used by operational verticals that send people to the field (emergency services, healthcare field teams, field services, delivery). An integration that only sends and syncs events does not need teams. A team is a field unit that wede can dispatch to an event: an ambulance crew, a technician squad, a courier team. Each team belongs to one tenant, has one primary vertical, an optional home zone and a list of members.

Authentication

All team endpoints need a session token (Authorization: Bearer <token>, see Login).

Operation	Permission	Tenant roles with it
Read teams	`teams:view`	`company_admin`, `company_tech`, `operational_supervisor`, `corporate_client`
Create, update, delete teams	`teams:manage`	`company_admin`, `company_tech`

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

The team object

string

Team UUID.

string

Tenant that owns the team.

string | null

UUID of the team’s home zone.

string

Team name, unique within your tenant.

string

Your own team type label, for example ADVANCED_LIFE_SUPPORT.

string

Primary vertical of the team, for example healthcare.

string[]

Free list of equipment labels stored on the team. Managed equipment with status and quantity lives in Team equipment.

string

available, on_mission or offline.

object[]

Returned by the list and get endpoints. Each member has id, name, role, status, lat, lng and last_seen.

string

ISO 8601 timestamp.

string

ISO 8601 timestamp.

List teams

GET /v1/teams

Returns every team of your tenant, ordered by name, with its members.

curl https://api.wede.pt/v1/teams \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN"

Response 200

{
  "data": [
    {
      "id": "259edc6e-95f3-42ba-bac5-263cfe51ebc0",
      "tenant_id": "9c145f7e-83be-4039-8e9c-650796acd3ee",
      "zone_id": "4f1c2a0e-6b1d-4a57-9d0e-2f1b7c3d8e21",
      "name": "Alpha Medical",
      "type": "ADVANCED_LIFE_SUPPORT",
      "vertical": "healthcare",
      "equipment": ["AED", "STRETCHER"],
      "status": "available",
      "created_at": "2026-06-01T09:00:00.000Z",
      "updated_at": "2026-06-09T18:00:00.000Z",
      "members": [
        {
          "id": "0b7e5d1c-3a2f-4e8b-9c6d-1f2e3a4b5c6d",
          "name": "Ana Costa",
          "role": "PHYSICIAN",
          "status": "available",
          "lat": 38.7169,
          "lng": -9.1399,
          "last_seen": "2026-06-09T17:58:00.000Z"
        }
      ]
    }
  ],
  "count": 1
}

Get a team

GET /v1/teams/{id}

string

required

Team UUID.

Returns the team object with its members.

curl https://api.wede.pt/v1/teams/259edc6e-95f3-42ba-bac5-263cfe51ebc0 \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN"

Create a team

POST /v1/teams

Requires teams:manage.

string

required

2 to 100 characters. Must be unique within your tenant.

string

required

2 to 50 characters.

string

required

2 to 50 characters.

string[]

Equipment labels.

string

UUID of an existing zone.

string

default:"available"

available, on_mission or offline.

curl -X POST https://api.wede.pt/v1/teams \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Alpha Medical",
    "type": "ADVANCED_LIFE_SUPPORT",
    "vertical": "healthcare",
    "zone_id": "4f1c2a0e-6b1d-4a57-9d0e-2f1b7c3d8e21"
  }'

Returns 201 with the team object (without members). wede sends the team.created webhook with { team_id, name, vertical }.

Update a team

PATCH /v1/teams/{id}

Requires teams:manage. Send only the fields you want to change: name, type, vertical, equipment, zone_id, status, with the same rules as on create. A body with no fields returns the team unchanged.

string

required

Team UUID.

curl -X PATCH https://api.wede.pt/v1/teams/259edc6e-95f3-42ba-bac5-263cfe51ebc0 \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "status": "offline" }'

Returns 200 with the updated team object. wede sends the team.updated webhook with { team_id, fields }, where fields lists the names of the fields you sent.

Delete a team

DELETE /v1/teams/{id}

Requires teams:manage. Only a team that was never sent on a mission can be deleted; deleting it also deletes its members, equipment and vertical settings. A team with missions is kept as their history: the call returns 409 team_has_missions. Set it unavailable instead.

curl -X DELETE https://api.wede.pt/v1/teams/259edc6e-95f3-42ba-bac5-263cfe51ebc0 \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN"

Returns 204 with no body. wede sends the team.deleted webhook with { team_id }.

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 `teams:view` or `teams:manage`, or you used an API key.
`404`	`not_found`	No team with this `id` in your tenant (get, update, delete). A team of another tenant is always answered with `404`, on every team endpoint.
`409`	`conflict`	A team with this `name` already exists in your tenant (create).
`409`	`team_has_missions`	The team has missions and is kept as their history (delete).
`500`	`internal_error`	Unexpected server error.

SDKs

listTeams and getTeam in JavaScript, list_teams and get_team in Python.

Overview

Authentication

Events

Teams & Dispatch

Missions

Zones

Billing

Tenant

Webhooks

Sync

Connectivity

Sandbox

Parsers

Onboarding

Authentication

The team object

List teams

Get a team

Create a team

Update a team

Delete a team

Errors

SDKs

​Authentication

​The team object

​List teams

​Get a team

​Create a team

​Update a team

​Delete a team

​Errors

​SDKs

Authentication

The team object

List teams

Get a team

Create a team

Update a team

Delete a team

Errors

SDKs