Events#
Event types are the registry of known event identifiers. There’s no explicit create endpoint — an event type is resolved-or-created the first time it’s referenced, either by an inbound POST /relay request or by a destination subscribing to it.
Authenticated with a management token.
List events#
GET /v0/eventsPaginated. See pagination .
Response 200
{
"limit": 25,
"previous": null,
"next": null,
"data": [
{
"id": "...",
"name": "order.placed",
"description": null,
"created_at": "2026-06-19T00:26:32.000+00:00",
"updated_at": "2026-06-19T00:26:32.000+00:00"
}
]
}Get an event#
GET /v0/events/{id}Response 200
{
"data": {
"id": "...",
"name": "order.placed",
"description": null,
"created_at": "2026-06-19T00:26:32.000+00:00",
"updated_at": "2026-06-19T00:26:32.000+00:00"
}
}Errors: 404 if the event doesn’t exist.
Update an event#
PATCH /v0/events/{id}Only description can be updated — the event name is immutable once created.
| Field | Rules |
|---|---|
description |
nullable, string |
Response 200 — same shape as GET /v0/events/{id}.
Errors: 404 if the event doesn’t exist, 422 on validation failure.