Skip to main content
Besides its primary vertical, a team can cover more verticals, each with a list of event types. wede uses these settings when it ranks teams for an incident with a vertical or event_type in the dispatch score.

Authentication

Session token (Authorization: Bearer <token>).
The integration API key (x-wede-api-key) has no teams:* permission. Calls with an API key return 403 forbidden.

The team vertical object

string
Record UUID.
string
Team UUID.
string
Your tenant.
string
Vertical code, for example healthcare.
string | null
UUID of the parser linked to this vertical for the team.
string[]
Event types the team handles in this vertical.
string
ISO 8601 timestamp.
string
ISO 8601 timestamp.

List team verticals

Returns { "data": [ ... ] }, ordered by vertical. Each item also has parser_name and parser_version when a parser is linked.
Response 200

Set a team vertical

Creates the vertical for the team, or replaces its event_types and parser_id if it already exists.
string
required
Team UUID.
string
required
Vertical code.
string[]
required
Event types the team handles in this vertical. Send [] for none.
string
UUID of one of your parsers. Omit it to clear the link.
Returns 200 with the team vertical object.

Remove a team vertical

Returns 204 with no body.

Errors