Events endpoints
Beta. All endpoints require a bearer API key with events:read. Response objects and examples are specified in OpenAPI.
List events
GET https://api.stello.no/v1/events
Returns a page of events owned by the key’s permitted organizations and allowed by its selected-event restriction. Every event in the list has the same event fields as the detail endpoint. Ticket types are separately paginated. Price summaries may be unavailable. All ticket types remain retrievable through their paginated endpoint.
| Parameter | Default | Accepted values and meaning |
|---|---|---|
status | published | Comma-separated statuses, or all. Statuses: draft, scheduled, published, unlisted, canceled, ended. |
time | current_or_upcoming | current_or_upcoming, current, upcoming, past, all. Independent of status. |
starts_at_gte | None | ISO 8601 timestamp with timezone; inclusive lower bound on event start. |
starts_at_lt | None | ISO 8601 timestamp with timezone; exclusive upper bound on event start. |
sort | starts_at | starts_at for ascending start, -starts_at for descending start. Equal starts use creation time in the same sort direction. |
limit | 20 | Integer from 1 to 100; maximum items returned per page. |
cursor | None | Opaque continuation token from the previous response. |
A parent key can include eligible sub-organization events through its per-key permission. These use the same endpoints and pagination, and retain their own org_id.
Archived events are internal to Stello and are excluded from every API endpoint, including status=all.
Filters are combined with AND. Multiple statuses are combined with OR. status=all cannot be combined with individual statuses. Unknown parameters, invalid values, duplicate parameters and contradictory date bounds return 400.
Status and time are separate
Time is evaluated against as_of, established by the first page:
| Time filter | Condition |
|---|---|
current_or_upcoming | ends_at > as_of |
current | starts_at <= as_of and ends_at > as_of |
upcoming | starts_at > as_of |
past | ends_at <= as_of |
all | No time restriction |
To get every allowed event, use both status=all and time=all. status=all alone still excludes past events; time=all alone still restricts status to published.
# Default website listing: published, ongoing and upcoming
/v1/events
# Upcoming published events only
/v1/events?time=upcoming
# All drafts, including those whose dates are past
/v1/events?status=draft&time=all
# Past events, including events whose lifecycle status has changed
/v1/events?status=all&time=past&sort=-starts_at
# Every event the key can access
/v1/events?status=all&time=all
# Published events starting during December in Oslo (UTC+01:00 then)
/v1/events?time=all&starts_at_gte=2026-11-30T23%3A00%3A00Z&starts_at_lt=2026-12-31T23%3A00%3A00ZPagination
{
"data": [],
"pagination": { "next_cursor": null, "has_more": false },
"as_of": "2026-11-09T12:00:00.000Z"
}Preserve the original parameters when adding cursor for the next page. Continue while has_more is true, even if a page contains fewer than limit records or is empty. The server may bound its scan before filling a page. Cursors are bound to the key, filters, sorting and limit, and expire after one hour. A changed query or invalid cursor returns 400 invalid_cursor; restart from page one.
as_of stays constant throughout a traversal so an event does not become past midway through the time filter. This is not a database snapshot. Concurrent edits, new events or deletions can change subsequent pages. Deduplicate by event ID and periodically refresh from the first page. Access changes apply at once to ticket checks, and within 30 seconds to other reads, which are briefly held at the edge (see caching and freshness).
Event IDs and codes
Every event has two stable identifiers, and any endpoint that takes {event_id} accepts either:
| Field | Example | Use |
|---|---|---|
id | k17f… (long) | The database ID. Use it as your record key. |
code | 4829167305 | A ten-digit code that is easier to copy, print, read out or put in a QR code. It is null for an event that has not been assigned one yet. |
Neither changes when the title or slug changes. The code is an identifier, not a secret, and grants no access by itself: the key’s permissions and event selection still apply.
To find an event’s ID or code, copy it from the event page in the dashboard, or list your events with GET /v1/events and read the id and code fields. GET /v1/events?time=all&starts_at_gte=…&starts_at_lt=… narrows the list to a date range.
Retrieve an event
GET https://api.stello.no/v1/events/{event_id}
Returns { "data": Event }. This endpoint has no status or time filters: knowing an allowed event’s ID lets the integration retrieve it even when it is a draft or past event.
Returns 404 for archived events, nonexistent events and events outside the key’s access. The endpoint accepts the stable ID, not a slug. Unknown query parameters return 400.
List an event’s ticket types
GET https://api.stello.no/v1/events/{event_id}/ticket-types
Returns { "data": TicketType[], "pagination": { ... }, "as_of": "..." }. Supports limit (default 20, maximum 100) and cursor. Order is sort_order ascending, then creation time ascending. Other parameters return 400.
All ticket types belonging to the allowed event can be retrieved, including drafts, archived, unlisted and till-only types. Use publicly_listed to select types for a public website. This endpoint is paginated so an event with many ticket types is still fully retrievable without an unbounded embedded array.
The parent event must be allowed by the key; otherwise the response is 404. Public listing and on-sale status are computed on each request, independently of the pagination as_of time. Inventory is advisory and is never held by an API read.
Retrieve a ticket
GET https://api.stello.no/v1/events/{event_id}/tickets/{ticket_id}
For booking systems that only accept ticket holders, for example for a room. The person gives your system the 7-character code printed under the QR on their ticket (or the ticket’s ID), and you ask Stello whether it counts. Requires a key with the Ticket lookup setting, and the event must be allowed for the key. It takes no query parameters.
{
"data": {
"id": "ticket_example",
"code": "98J5WS9",
"object": "ticket",
"event_id": "event_example",
"ticket_type": { "id": "ticket_type_example", "name": "Medlem" },
"status": "active",
"valid": true,
"checked_in": false,
"checked_in_at": null,
"as_of": "2026-11-19T14:00:00.000Z"
}
}valid is true for an active ticket, or one already checked in (used), to an event that is not canceled. Refunded, released and expired tickets are returned with valid: false and their status.
{ticket_id}is the ticket’s ID, or the code printed under its QR: seven letters and digits, in any case. A code is unique within its event, so it names one ticket. Should two tickets of an event ever be found with the same code you get409 ambiguous_ticket_code, never a guess, and the ticket’s ID always works.codein the response is the code on the ticket.- A ticket only answers under its own event. A ticket that belongs to another event, or does not exist, gets
404, the same answer for both. - The response never includes a name, email, the holder’s ID or the QR code.
- There is no endpoint that lists tickets, and none that searches by person. You can only look up a ticket whose ID you were given.
- Whoever gives you a ticket ID is not proven to be its holder. Treat the ID like a ticket number: use it to check the ticket, and confirm the person in your own system.
- Lookups count against the key’s normal rate limit. Check at booking time rather than on every keystroke.