REST API reference

Two endpoints, each dispatching on an "action" parameter over GET or POST. Responses are JSON and preserve the surrounding context — venue, organizer, schedule, ticket path — rather than returning a bare row.

Events API actions

GET or POST https://long.events/functions/v1/api-events with an "action" parameter.

discover: Search events by city, date window, category, coordinates, or free text. Each event carries catalog rank, predicted_end_time when the listing omitted an end, and ticket_offer when a verified price is still fresh.
list: Page through the catalog with stable ordering.
stats: Counts by city, source, and category for the current catalog.
catalog_stats: Coverage totals across cities, sources, and upcoming windows.
spotlight_candidates: Events that clear the editorial quality bar for a city.
get_sets: Set times for one event, in the venue’s local clock.
get_now_playing: What is on stage right now at a given event.
get_schedule: The full stage-by-stage programme for one event.
search_artists: Find artists by name, with identity disambiguation.
get_artist: One artist profile, including verified external identities.
get_artist_events: Upcoming and past dates for a named artist.
list_artists: Page through the artist index.

Event Weeks API actions

GET or POST https://long.events/functions/v1/api-event-weeks with an "action" parameter.

list: Page through conference weeks and festivals.
get: One event week with its full linked side-event programme.
search: Find event weeks by name, city, or tag.
cities: Cities that currently host an event week.
tags: The event-week tag vocabulary.

Event descriptions

Event descriptions returned by api-events and in event-week side-event listings are plain text. Source HTML and escaped markup are removed, supported HTML entities are decoded, and paragraph breaks are preserved. Treat the text as content rather than rendering it as HTML.

Requests and authentication

Send the API key in X-API-Key. A request without a key that targets a metered action returns HTTP 402 with machine-readable payment requirements instead of an error page; satisfy them and repeat the identical request to receive the data plus a PAYMENT-RESPONSE settlement header.

Generated clients

The OpenAPI 3.1 document at https://long.events/openapi.json describes every action, parameter and response schema, and its action enums are tested against the live handlers.