Skip to main content
The type of an event is an active event type of your catalog for the event’s vertical, for example cardiac_arrest. Anything else returns 422 unknown_event_type, with the accepted codes in known_types. Your catalog is organised by vertical: each vertical has categories, each category has event types, and each type says whether it sends a field team and which equipment or qualifications resolve it. wede pre-loads a starting catalog for every vertical of your organisation; your administrators keep what fits, add their own and deactivate what they do not use, in the dashboard (Catalog) or with a session token. API keys can read it.
Before 8 October 2026 an event could also carry a wede category (EMERGENCY, PAYMENT, OTHER and others) as its type. Those codes are no longer accepted: send a type of your catalog. GET /v1/event-categories now returns an empty list and will be removed.

Read your catalog

Authentication

API key, or session token with the teams:view permission. API keys have catalog:view, which allows this call.

Query parameters

string
Return only this vertical, for example healthcare.

Example

Response

200 OK. One entry per vertical of your organisation, with its categories and their types, active and inactive.
object[]

Errors

Equipment and qualifications

One list for the whole organisation, used by event types (what resolves them) and by teams (what they have). Same authentication as above.
kind is equipment or qualification. Pass active=true to get only active items.

Managing the catalog

Administrators manage the catalog in the dashboard. The same operations are available with a session token that has the teams:manage permission: POST, PATCH and DELETE on /v1/catalog/categories/:id, /v1/catalog/types/:id and /v1/catalog/equipment/:id, and POST /v1/catalog/reseed to add back any wede default that was deleted (it never changes what you have). A type cannot be deleted while it has open events (409 type_has_open_events) or a parser points to it (409 type_used_by_parser); deactivate it instead. A type can only require equipment that exists in your list (422 unknown_equipment).

Types, parsers and teams

Each value of the type field of a parser points to a type of your catalog, so a message that arrives by SMS or another degraded channel creates an event with the same type as one sent online. A parser cannot be activated while one of its values points to a type that does not exist. Teams cover a whole category or specific types. Only teams that cover the type of an event are candidates for its dispatch; a type’s required_equipment lowers the score of teams that lack it and never excludes them. See Score engine.