SeeTickets APIsee tickets.com ↗
Access SeeTickets.com event listings, venue details, ticket options, and category browsing via a structured API. 5 endpoints covering search, suggestions, and more.
What is the SeeTickets API?
The SeeTickets.com API provides access to live event data across 5 endpoints, covering everything from full-text event search to venue calendars and category browsing. The get_event_details endpoint returns ticket types with face-value and total pricing, availability status, and individual tour dates for multi-show listings. Whether you need autocomplete suggestions or a structured list of upcoming events at a specific venue, this API surfaces real fields from SeeTickets' catalog.
curl -X GET 'https://api.parse.bot/scraper/f20e756e-dbea-4f61-8ea8-4a63f89e7ade/search_events?q=concert&page=1&limit=10&query=concert&offset=0' \ -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 seetickets-com-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.
"""Walkthrough: See Tickets SDK — search events, explore details, browse categories."""
from parse_apis.see_tickets_api import SeeTickets, Category, ResourceNotFound
client = SeeTickets()
# Search for concert events, capped at 5 results
for event in client.events.search(query="concert", limit=5):
print(event.name, event.date, event.location)
# Get autocomplete suggestions for a partial term
group = client.suggestiongroups.search(query="rock", limit=1).first()
if group:
print(group.title, len(group.results))
for suggestion in group.results[:3]:
print(suggestion.name, suggestion.events_counter)
# Browse a category using the enum
listing = client.categorylistings.get(category=Category.MUSIC)
print(listing.category, len(listing.artists))
for artist in listing.artists[:3]:
print(artist.name, artist.url)
# Get detailed event/tour info with typed-error handling
try:
detail = client.eventdetails.get(url="/tour/punk-rock-factory")
print(detail.name, len(detail.sub_events))
for sub in detail.sub_events[:2]:
print(sub.name, sub.date, sub.location)
except ResourceNotFound as exc:
print(f"not found: {exc}")
# Get venue details
venue = client.venues.get(url="/venue/rock-city-nottingham/469")
print(venue.name, venue.address)
for ev in venue.upcoming_events[:3]:
print(ev.name, ev.date)
print("exercised: events.search / suggestiongroups.search / categorylistings.get / eventdetails.get / venues.get")
Full-text search over See Tickets event listings. Returns paginated results matching the query keyword across event names, venues, and descriptions. Each result includes the event name, URL, date, location, and image. Pagination via integer page number; 30 results per page.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| queryrequired | string | Search keyword to find events (e.g. 'concert', 'rock', 'theatre'). |
{
"type": "object",
"fields": {
"query": "string, the search query used",
"results": "array of event objects with name, url, date, location, image_url",
"total_pages": "integer, total number of pages available",
"current_page": "integer, current page number"
},
"sample": {
"data": {
"query": "concert",
"results": [
{
"url": "https://www.seetickets.com/event/outlander-in-concert/glasgow-royal-concert-hall/3621114",
"date": "Mon 15 Feb 2027",
"name": "Outlander in Concert",
"location": "Outlander in Concert Glasgow Royal Concert Hall, Glasgow Mon 15 Feb 2027 , 20:00",
"image_url": null
}
],
"total_pages": 10,
"current_page": 1
},
"status": "success"
}
}About the SeeTickets API
Search and Discovery
The search_events endpoint accepts a query string and returns up to 30 results per page, with total_pages and current_page fields for pagination. Each result in the results array includes name, url, date, location, and image_url. For building type-ahead interfaces, get_search_suggestions accepts a partial query and returns grouped suggestions under categories like Events, Venues, and Locations — each entry carrying Name, Url, ImgUrl, Category, and EventsCounter.
Event and Venue Details
The get_event_details endpoint takes a url parameter (either a full URL or a path like /tour/punk-rock-factory) and returns structured data including Open Graph meta fields, a tickets array with type, price_total, price_face_value, and availability, and a sub_events array listing individual tour dates with name, url, date, and location. For single-event pages the description field provides text copy. The get_venue_details endpoint takes a venue URL and returns name, address (with postcode), and upcoming_events as an array of objects with ISO datetime strings.
Category Browsing
The browse_category endpoint accepts one of seven fixed category values — music, theatre, comedy, sport, festivals, attractions, or events — and returns two arrays: featured (promotional items with name and url) and artists (grid listings with name, url, and image). This is useful for building landing pages or category-level event directories without needing a search query.
Coverage and Data Shape
SeeTickets primarily covers UK and US events. Event dates are returned as strings from search_events and as ISO datetime strings from get_venue_details. The tickets array from get_event_details distinguishes price_face_value from price_total, which is useful for identifying booking-fee margins. Tour pages and single-event pages share the same endpoint but populate different fields — tour pages populate sub_events while single-event pages populate tickets.
The SeeTickets API is a managed, monitored endpoint for see tickets.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when see tickets.com 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 see tickets.com 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?+
- Aggregate upcoming UK and US concerts and theatre shows into a local events app using
search_eventswith genre keywords. - Build a type-ahead event search UI using the
get_search_suggestionsendpoint's groupedEvents,Venues, andLocationsresults. - Display full ticket pricing breakdowns — face value vs. total cost — by calling
get_event_detailsfor any event or tour URL. - Show a venue's complete upcoming event calendar with ISO-formatted dates using
get_venue_details. - Populate category landing pages for music, comedy, or festivals using the
browse_categoryendpoint'sfeaturedandartistsarrays. - Track ticket availability changes over time by periodically polling
get_event_detailsfor theavailabilityfield on specific ticket types. - Map tour routing for an artist by extracting
sub_eventsfrom a tour page viaget_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 SeeTickets have an official public developer API?+
What does `get_event_details` return differently for tour pages versus single-event pages?+
sub_events array is populated with individual show dates, venues, and URLs, while tickets may be sparse. For single-event pages, tickets is populated with type, price_face_value, price_total, and availability — and sub_events will typically be empty.Does the API return artist or performer details such as bios, social links, or discography?+
How does pagination work in `search_events`?+
total_pages and current_page integers. Pass the integer page parameter to retrieve subsequent pages. There is no cursor-based pagination — only numeric page offsets.Does the API cover events outside the UK and US, or filter by geographic region?+
search_events query or by calling get_venue_details for a specific venue URL. You can fork this API on Parse and revise it to add location-based filtering if finer geographic control is needed.