seatgeek.com APIseatgeek.com ↗
Access SeatGeek event data: search events, get ticket price stats, browse performers and venues, and retrieve trending events via 8 structured endpoints.
curl -X GET 'https://api.parse.bot/scraper/b1da66dd-8dbd-4b3e-b9da-bafebaa20ad3/search_events?query=concert&per_page=3' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for events by keyword/name, returning event titles, dates, venues, categories, performers, and ticket price statistics. Supports filtering by taxonomy, location, and pagination.
| Param | Type | Description |
|---|---|---|
| lat | string | Latitude for location-based search |
| lon | string | Longitude for location-based search |
| page | integer | Page number for pagination |
| query | string | Search keyword or event name |
| per_page | integer | Results per page |
| taxonomy_id | string | Category/taxonomy ID to filter events by (e.g. '1000000' for Sports, '2000000' for Concerts) |
{
"type": "object",
"fields": {
"meta": "object with total count, page, per_page, and geolocation info",
"events": "array of event objects with id, title, datetime_utc, venue, performers, stats (prices), taxonomies, and url"
},
"sample": {
"data": {
"meta": {
"page": 1,
"total": 15,
"per_page": 3
},
"events": [
{
"id": 18179429,
"stats": {
"lowest_price": 96,
"median_price": 105,
"highest_price": 114,
"listing_count": 2
},
"title": "Love Story - A Tribute to Taylor Swift",
"venue": {
"id": 153259,
"city": "DeLand",
"name": "Athens Theatre",
"state": "FL"
},
"performers": [
{
"id": 1959461,
"name": "Love Story - Taylor Swift Tribute Band"
}
],
"datetime_utc": "2026-05-15T23:30:00"
}
]
},
"status": "success"
}
}About the seatgeek.com API
The SeatGeek API exposes 8 endpoints covering event search, ticket pricing, performer lookup, venue schedules, and category taxonomies. The search_events endpoint returns event titles, UTC datetimes, venue details, performer arrays, and price statistics (lowest, highest, median, average) in a single paginated response. You can filter by keyword, taxonomy ID, or geographic coordinates to narrow results to a specific market or event type.
Event Search and Detail
The search_events endpoint accepts a query string, optional lat/lon coordinates, a taxonomy_id (e.g. 1000000 for Sports, 2000000 for Concerts), and pagination controls (page, per_page). Each returned event object includes id, title, datetime_utc, a venue object (name, city, state, coordinates), a performers array, a stats block with lowest_price, highest_price, median_price, and average_price, plus direct url. For a single event, get_event_detail takes an event_id and returns the same shape with full configuration and schedule status fields.
Pricing and Ticket Listings
get_event_ticket_prices_summary returns an isolated stats object for a given event_id, covering listing_count, average_price, lowest_price, highest_price, median_price, lowest_sg_base_price, and visible_listing_count — useful when you only need the pricing snapshot without pulling the full event record. For row-level granularity, get_event_ticket_listings returns an array of individual listings with section, row, seat, and price data alongside a num_listings count.
Performers, Venues, and Taxonomies
search_performers takes a required query and optional limit, returning performer objects with id, name, type, score, slug, genres, popularity, has_upcoming_events, and num_upcoming_events. Once you have a venue ID from any event object, get_venue_events lists all upcoming events at that venue with the same full event shape including stats. get_taxonomies requires no inputs and returns the full category tree — each taxonomy carries id, name, parent_id, slug, and a stats block with event_count and performer_count. get_trending_events supports optional lat/lon to surface location-aware trending content.
- Track ticket price floors and ceilings across upcoming concerts using
stats.lowest_priceandstats.highest_pricefromsearch_events - Build a venue calendar by calling
get_venue_eventswith a venue ID to list all scheduled events at a specific arena or theater - Monitor performer popularity scores and upcoming event counts via
search_performersto identify rising or peaking acts - Filter local sports events by passing taxonomy_id
1000000alongside lat/lon coordinates insearch_events - Compare median ticket prices across multiple events using
get_event_ticket_prices_summarywithout fetching full event detail payloads - Populate a category navigation using the full taxonomy tree from
get_taxonomies, including parent/child relationships and per-category event counts - Surface location-relevant trending events by passing user coordinates to
get_trending_events
| 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 | 250 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 SeatGeek have an official developer API?+
What does `get_event_ticket_listings` return compared to `get_event_ticket_prices_summary`?+
get_event_ticket_listings returns an array of individual listings with per-seat data (section, row, seat, price) and a num_listings count. get_event_ticket_prices_summary returns only aggregate stats: lowest_price, highest_price, median_price, average_price, listing_count, lowest_sg_base_price, and visible_listing_count. Use the summary endpoint when you need price range context without iterating individual seats.Does the API expose historical pricing or sold-out event data?+
Can I filter `search_events` results to a specific city without knowing the exact coordinates?+
search_events endpoint filters by lat and lon string parameters for location-based search; there is no city-name filter parameter. You would need to resolve a city name to coordinates before passing them. The meta response object includes geolocation info from the query. Direct city-name filtering is not currently exposed as a parameter, but you can fork the API on Parse and revise it to add a geocoding step or a city-name input.How is `taxonomy_id` used in `search_events`, and where do valid IDs come from?+
taxonomy_id is an optional string filter on search_events that restricts results to a category — for example 1000000 for Sports or 2000000 for Concerts. The full list of valid IDs, names, slugs, and parent relationships comes from calling get_taxonomies, which requires no inputs and returns every category with its id field.