Skip to Content
Quickstart

Quickstart

Beta — these endpoints are in beta. Ask Stello to enable access for your organization.

Get access

Ask Stello to enable API access for your organization. Once enabled, an organization admin will be able to create a named API key in the dashboard’s developer settings.

Choose Events to grant access to all current and future events, or restrict the key to selected events. Set activation and expiration dates. A key without an expiration date is supported, with a warning in the dashboard.

Copy the secret when it is created. It is shown once. Store it in a server-side environment variable or secret manager:

STELLO_API_KEY=your_secret_key

Never use a browser-exposed environment variable such as NEXT_PUBLIC_STELLO_API_KEY. Do not commit the secret or put it in a URL.

List events for your website

Proposed base URL: https://api.stello.no/v1.

curl --fail-with-body 'https://api.stello.no/v1/events?limit=20' \ --header "Authorization: Bearer $STELLO_API_KEY"

The response has this structure. This empty response is a valid result when no events match:

{ "data": [], "pagination": { "next_cursor": null, "has_more": false }, "as_of": "2026-11-09T12:00:00.000Z" }

Without filters, the list contains only published events whose ends_at is later than as_of. New events appear automatically after publication when the key has unrestricted Events access.

Retrieve an event

curl --fail-with-body "https://api.stello.no/v1/events/$EVENT_ID" \ --header "Authorization: Bearer $STELLO_API_KEY"

The response is { "data": { ...event fields... } }. Use stable event IDs when storing or retrieving records; titles and slugs can change.

Retrieve every event

curl --fail-with-body 'https://api.stello.no/v1/events?status=all&time=all&limit=100' \ --header "Authorization: Bearer $STELLO_API_KEY"

Follow pagination.next_cursor until it is null. This includes drafts, scheduled, unlisted, canceled, ended and archived events, subject to the key’s selected-event restriction. These results are private integration data: do not publish the entire response on a public website.

See the website guide for a server-side example, ticket pricing and publication rules.

Usage terms

By accessing or using the API, you accept the API terms. They cover permitted integrations, security, data use and restrictions on misuse or platform replication.