q, city, two-letter country, lat, lng and radius in miles.
Discover events
No API key is required for the current read-only public discovery surface. Requests are rate limited by client address and responses are cacheable.
GET
/api/v1/events?country=GB&city=London&page=1&per_page=24Retrieve one event with its public ticket options using /api/v1/events/{slug}.
Filters that compose
category, tag, free and when for today, weekend or month.
Use sort=trending or sort=newest. The default prioritises promoted events then upcoming date.
page starts at 1. per_page defaults to 24 and is capped at 50.
Stable public event representation
Event responses use the versioned nawhe.event contract introduced in v1.7.4. It keeps organiser identity, lifecycle, location visibility, artwork, admission, ticket state and booking actions consistent with the public event experience.
GET
/api/v1/openapi.jsonRate limits, caching and pagination
The public API allows 120 requests per 60-second window per client address. Rate-limit headers report the limit and remaining requests. Event lists are cached for 60 seconds; event detail for 120 seconds; categories and tags for 5 minutes.
Responses include ETag and support If-None-Match, allowing unchanged resources to return 304 Not Modified. The discovery result window is currently capped at 500 matching events per query; use narrower location, date, category or tag filters for large inventories.
Public data only
The API deliberately excludes attendee records, booking/customer details, promoter user IDs, payment credentials, payout configuration, internal audit data and private venue coordinates. If an exact address is configured to appear only after booking, the API preserves that protection.