Search by words, city, country or nearby area.
Public fields:q, city, country, lat, lng, radiusSearch published events, read public event details and send people to the right ticket option. Private attendee, organiser-account and payment information is not included.
The public API can be used without an account key at the moment. Begin with the event search address below, then add the filters your product needs.
/api/v1/events?country=GB&city=London&page=1&per_page=24To read one event and its public ticket options, request /api/v1/events/{slug}.
Search by words, city, country or nearby area.
Public fields:q, city, country, lat, lng, radiusNarrow results by category, tag, free admission or when the event is happening.
Public fields:category, tag, free, whenChoose trending or newest events, or use the normal upcoming-event order.
Public field:sortMove through results in pages rather than loading a very large list at once.
page starts at 1; per_page supports up to 50Responses are designed to match what people can see on nawhe?: event identity, organiser name, dates, visible location information, artwork, admission details, ticket availability and the current booking action.
/api/v1/openapi.jsonThe public specification above describes the available fields and response shapes for integrations that need a machine-readable reference.
The service currently allows up to 120 requests in a 60-second period for each connecting address. List results may be kept for up to 60 seconds, event details for up to 120 seconds, and categories or tags for up to five minutes.
Large searches should use location, date, category or tag filters and move through pages. This keeps responses quick and avoids requesting more information than a visitor needs at once.
The API does not provide attendee details, private account information, payment or payout information, internal administration records, or a venue address that an organiser has chosen to reveal only after booking.