AllEvents APIallevents.in ↗
Access event listings, details, venue data, and category filters from AllEvents.in across cities worldwide. 4 endpoints covering search, dates, and details.
What is the AllEvents API?
The AllEvents.in API gives developers access to event data across cities worldwide through 4 endpoints covering search, date-range filtering, detailed event records, and category discovery. The search_events endpoint returns event listings with names, start and end times, venue, location, ticket availability indicators, and banner images. Use get_event_details to retrieve structured fields including address, coordinates, ticket currency, and ISO-formatted dates for a specific event page.
curl -X GET 'https://api.parse.bot/scraper/9a478cf5-ac7c-432e-ae6f-e1b964932cd5/search_events?city=London&limit=5&category=music' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace allevents-in-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""AllEvents SDK — discover events by city, category, and date range."""
from parse_apis.allevents_api import AllEvents, City_, EventNotFound
client = AllEvents()
# Browse available categories for London
london = client.city("London")
for cat in london.categories(limit=5):
print(cat.name, cat.count)
# Search music events in London
event = london.search(category="music", limit=1).first()
if event:
print(event.name, event.start_time_display)
print(event.venue.full_address)
print(event.tickets.has_tickets, event.tickets.ticket_currency)
# Drill into full event details
try:
detail = event.details()
print(detail.description_text[:120] if detail.description_text else "No description")
print(detail.ticket_purchase_url)
except EventNotFound as exc:
print(f"Event gone: {exc.event_url}")
# Search events by date range
for ev in london.search_by_date(start_date="2026-07-01 00:00", end_date="2026-07-31 23:59", limit=3):
print(ev.name, ev.location, ev.start_time_display)
print("exercised: city.categories / city.search / event.details / city.search_by_date")
Search for events in a city by category. Returns a paginated list of events with basic info including name, dates, venue, and ticket availability. Paginates by adjusting limit. Each event includes a nested venue object with geographic coordinates and a tickets object indicating availability.
| Param | Type | Description |
|---|---|---|
| cityrequired | string | City name to search events in (e.g. "London", "New York", "Tokyo"). |
| limit | integer | Maximum number of events to return. |
| category | string | Event category slug to filter by. Use get_categories endpoint to discover available slugs for a city. Common values include "entertainment", "music", "art", "parties". |
{
"type": "object",
"fields": {
"city": "string, resolved city name",
"count": "integer, number of events returned",
"events": "array of Event objects with event_id, name, start_time_display, end_time_display, location, venue, event_url, banner_url, organizer, tickets, categories, tags",
"country": "string, resolved country name"
},
"sample": {
"data": {
"city": "London",
"count": 3,
"events": [
{
"name": "Harry Styles at Wembley Stadium",
"tags": [
"adventure"
],
"venue": {
"city": "London",
"state": "EN",
"street": "Royal Route, London, HA9 7EX",
"country": "United Kingdom",
"latitude": "51.556034",
"longitude": "-0.285558",
"full_address": "Wembley Stadium, Royal Route, London, HA9 7EX, United Kingdom"
},
"tickets": {
"ticket_url": "",
"has_tickets": false,
"ticket_currency": "GBP"
},
"event_id": "2400029570211030",
"location": "Wembley Stadium",
"event_url": "https://allevents.in/london/harry-styles-at-wembley-stadium/2400029570211030",
"organizer": {
"name": "Vivid Events",
"org_id": "22309944"
},
"banner_url": "https://cdn-ip.allevents.in/s/rs:fill:500:250/g:sm/sh:100/example.avif",
"categories": [
"trips-adventures"
],
"end_time_display": "Fri, 12 Jun at 05:00 pm",
"start_time_display": "Fri, 12 Jun at 05:00 pm"
}
],
"country": "United Kingdom"
},
"status": "success"
}
}About the AllEvents API
Searching Events by City and Category
The search_events endpoint accepts a required city string and optional category and limit parameters. The response includes a resolved city and country name, a count of returned results, and an array of event objects. Each event object carries event_id, name, start_time_display, end_time_display, venue, location, event_url, banner_url, and organizer information. Category slugs (e.g. "music", "art", "entertainment") can be discovered via the get_categories endpoint, which returns a list of objects with slug, name, and count fields for the specified city.
Filtering Events by Date Range
The search_events_by_date endpoint works similarly to search_events but replaces the category filter with start_date and end_date inputs, both in "YYYY-MM-DD HH:MM" format. This makes it straightforward to build calendar-style views or narrow results to a weekend, a specific week, or a multi-week window. The response shape mirrors the category search: resolved city and country, a count, and the same event object array.
Retrieving Event Details
Passing a full event_url to get_event_details retrieves structured fields for a single event: name, venue, address, city, country, start_date, end_date (both ISO-formatted), latitude, longitude, currency, and ticket-related data when available. The endpoint notes that fields vary by event source — not every event will populate every field. Coordinates and address data are particularly useful for mapping integrations. Obtain valid event URLs from the event_url field returned by the search endpoints.
City Category Discovery
The get_categories endpoint is city-scoped. Passing a city name returns every category active in that city along with a count of available events per category and a total_rows integer. This is the intended way to populate a category picker before calling search_events, since valid slugs differ by city and some categories exist only in certain markets.
The AllEvents API is a managed, monitored endpoint for allevents.in — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when allevents.in changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official allevents.in API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a local event discovery feed filtered by category (e.g. 'music' or 'art') for a given city using
search_events. - Power a weekend-activity planner by querying
search_events_by_datewith Friday-to-Sunday date bounds. - Display a venue map by collecting
latitudeandlongitudefrom multipleget_event_detailscalls. - Aggregate event banner images and names for a city homepage using the
banner_urlandnamefields from search results. - Populate a category filter UI by calling
get_categorieson user-selected cities to list only active event types. - Track ticket currency and availability across cities by parsing the
currencyfield returned in event detail responses. - Sync event start and end times to a calendar application using the ISO
start_dateandend_datefields fromget_event_details.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does AllEvents.in offer an official developer API?+
What does `get_event_details` return compared to the search endpoints?+
get_event_details adds structured fields available on the individual event page — ISO-formatted start and end dates, street address, latitude, longitude, and ticket currency code. Not all fields are populated for every event; availability depends on what the event listing includes.Are there limitations on which cities return results?+
get_categories endpoint is the practical way to check what's actually available in a given city before building queries against it — cities with sparse coverage may return few or no categories.Does the API support free-text keyword search for event names?+
search_events filters by city and category slug, and search_events_by_date filters by city and date range. You can fork this API on Parse and revise it to add a keyword search endpoint if your use case requires name-based filtering.Can I retrieve paginated results beyond the `limit` parameter?+
limit parameter to cap the number of results returned, but there is no pagination offset or cursor parameter currently available. You can fork this API on Parse and revise it to add offset or page-based pagination support.