stubhub.com APIstubhub.com ↗
Access StubHub ticket listings, event details, performer schedules, and marketplace discovery via 5 structured API endpoints with pricing and seat data.
curl -X GET 'https://api.parse.bot/scraper/781a7acb-7269-4afa-81c0-0ef1ef109043/search_autocomplete?query=Taylor+Swift' \ -H 'X-API-Key: $PARSE_API_KEY'
Get trending performer and event suggestions from StubHub. Returns popular categories with their names, IDs, relative URLs, and thumbnail images. Note: results reflect currently trending performers rather than query-filtered matches.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword (e.g., 'Taylor Swift') |
{
"type": "object",
"fields": {
"data": "array of suggestion objects, each containing id, tlcId, title, url, and categoryImageUrl"
},
"sample": {
"data": {
"data": [
{
"id": 70763,
"url": "/noah-kahan-tickets/performer/100276660",
"title": "Noah Kahan",
"tlcId": 3,
"categoryImageUrl": "https://media.stubhubstatic.com/stubhub-v2-catalog/d_defaultLogo.jpg/q_auto:low,f_auto,c_thumb,g_auto,w_108,h_108/categories/70763/6582979"
}
]
},
"status": "success"
}
}About the stubhub.com API
The StubHub API covers 5 endpoints for querying ticket marketplace data — from trending performer suggestions to per-listing seat and price details. The get_event_details endpoint returns individual ticket listings with section, row, seat, deal score, and a venue section map, while get_performer_events surfaces upcoming event dates, venue names, and minimum prices for any performer or team on the platform.
Event and Ticket Data
The get_event_details endpoint accepts an event_id and event_slug and returns every active ticket listing for that event. Each listing object includes section, row, seat, price, availableTickets, and a dealScore that reflects relative value within the listing set. A venue_map object provides a section-keyed breakdown of pricing and availability, and pricing_summary gives you min_price and max_price at a glance. The event_slug and event_id needed as inputs can be obtained directly from get_performer_events or browse_category_components response URLs.
Performer and Discovery Endpoints
get_performer_events takes a performer_id and performer_slug and returns the full upcoming event schedule for that performer, including eventName, localEventDate, localEventTime, venueName, and minPrice per event, alongside a totalCount of scheduled events. It also returns an altPerformersCarousel of related performers with images and category IDs, useful for building recommendation flows. search_autocomplete returns trending categories with id, tlcId, title, url, and categoryImageUrl — note that results reflect platform-trending performers, not query-filtered matches.
Search and Browse
search_events accepts a free-text query and returns resultsWithMetadata grouping events, performers, and venues in structured result groups. browse_category_components accepts the method value DontMissEvents and returns homepage-carousel events inferred by location, each with eventId, eventName, url, localEventDate, localEventTime, venueName, and minPrice. These two endpoints are the primary entry points for discovery when you don't yet have a performer ID or event slug.
- Build a ticket price tracker that monitors
min_priceandmax_pricefromget_event_detailsacross multiple events over time. - Aggregate performer schedules by calling
get_performer_eventsto populate tour date calendars with venue and date data. - Compare seat-level deal scores across listings for a single event to surface the best-value tickets by section.
- Populate an event recommendation widget using
altPerformersCarouselimages and names from the performer endpoint. - Discover locally trending events without a specific search query using
browse_category_componentswith theDontMissEventsmethod. - Feed
search_eventsquery results into a venue-specific event aggregator by filteringresultsWithMetadatafor venue result groups. - Resolve performer IDs from
search_autocompleteURL paths for downstream use inget_performer_eventscalls.
| 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 StubHub have an official public developer API?+
What does `search_autocomplete` actually return, and does it filter by the query I send?+
id, tlcId, title, url, and categoryImageUrl. The results reflect currently trending performers on the platform rather than query-filtered matches, so the query parameter influences context but does not guarantee results scoped to that exact search term.Does the API support pagination for large event listing sets?+
get_event_details endpoint returns a listings_count integer and the full listing array for that request, but there is no paginated offset or cursor parameter exposed. For performers with many upcoming events, get_performer_events returns a totalCount alongside the items array, but page-through iteration is not currently supported. You can fork the API on Parse and revise it to add pagination parameters to either endpoint.Can I retrieve sold listings or historical ticket sale prices?+
get_event_details, and upcoming event schedules with minimum prices via get_performer_events. You can fork the API on Parse and revise it to add an endpoint targeting historical sales data if that surface becomes accessible.Are venue seat maps or arena diagrams returned by the API?+
venue_map field in get_event_details provides a sectionPopupData object mapping section keys to pricing and availability summaries — this is structured section-level data, not a graphical seat map image. Full interactive arena diagrams are not part of the response. You can fork the API on Parse and revise it to surface additional venue layout data if needed.