StubHub APIstubhub.com ↗
Access StubHub ticket listings, event details, performer schedules, and trending suggestions via 5 structured API endpoints. No scraping required.
What is the StubHub API?
The StubHub API exposes 5 endpoints covering ticket marketplace data including event search, live ticket listings with seat-level pricing, and performer schedules. The get_event_details endpoint returns individual ticket listings with fields like section, row, seat, price, availableTickets, and dealScore, plus a venue section map summarizing pricing ranges across the arena. IDs and slugs needed by most endpoints are discoverable from search_autocomplete and search_events responses.
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'
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 stubhub-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.
from parse_apis.stubhub_ticket_api import StubHub, ComponentMethod, Performer
stubhub = StubHub()
# Browse trending events near the user's location
for event in stubhub.events.browse(method=ComponentMethod.DONT_MISS_EVENTS, limit=5):
print(event.event_name, event.venue_name, event.local_event_date, event.min_price)
# Search for suggestions by keyword
for suggestion in stubhub.suggestions.search(query="Coldplay", limit=5):
print(suggestion.title, suggestion.url, suggestion.tlc_id)
# Search for events and performers grouped by entity type
for group in stubhub.matchgroups.search(query="Lakers"):
for match in group.results:
print(match.title, match.subtitle, match.url)
# Get events for a specific performer via constructible resource
performer = Performer(_api=stubhub, performer_id="2864", performer_slug="denver-nuggets-tickets")
for event in performer.events(limit=3):
print(event.event_name, event.venue_name, event.local_event_date)
# Navigate to sub-resource: listings for this event
for listing in event.listings.list(limit=5):
print(listing.section, listing.row, listing.raw_price, listing.is_cheapest_listing)
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', 'Lakers') |
{
"type": "object",
"fields": {
"data": "array of suggestion objects, each containing id, tlcId, title, url, and categoryImageUrl"
},
"sample": {
"data": {
"data": [
{
"id": 177764,
"url": "/matt-rife-tickets/category/130402730",
"title": "Matt Rife",
"tlcId": 1,
"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/177764/6582698"
}
]
},
"status": "success"
}
}About the StubHub API
Search and Discovery
The search_autocomplete endpoint accepts a keyword query and returns trending performer and event suggestions, each with an id, tlcId, title, url, and categoryImageUrl. Note that results reflect currently trending performers on StubHub rather than strict query-filtered matches — a search for a lesser-known act may return trending alternatives instead. The search_events endpoint runs a full search and returns results grouped by entity type: performers (entity=5), events (entity=2), and venues (entity=3), each group carrying titles, URLs, and image URLs.
Event and Ticket Details
Once you have an event_id and event_slug — both parseable from URL paths in search results — get_event_details returns the complete active ticket inventory for that event. Each listing object includes section, row, seat, price, availableTickets, and dealScore. The venue_map field provides a sectionPopupData map keyed by section, giving per-section pricing and availability summaries useful for building seat-map visualizations. A pricing_summary object with min_price and max_price floats gives an at-a-glance range without iterating all listings.
Performer Schedules and Browse
get_performer_events takes a performer_id and performer_slug (both available from search_autocomplete URL paths) and returns upcoming events with fields including eventId, eventName, url, localEventDate, localEventTime, venueName, and minPrice. It also returns an altPerformersCarousel with related performer names, images, and IDs, and a maybeInterestedInCarousel for discovery. The browse_category_components endpoint, limited to the DontMissEvents method, returns a location-inferred carousel of upcoming events with the same core event fields.
The StubHub API is a managed, monitored endpoint for stubhub.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when stubhub.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 stubhub.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?+
- Monitor StubHub price floors for a specific event using
min_priceandmax_pricefromget_event_details. - Build a performer tour tracker by pulling upcoming event dates, venues, and ticket prices via
get_performer_events. - Aggregate section-level ticket availability across an arena using
venue_map.sectionPopupDatafromget_event_details. - Surface trending performers in a local events app using
search_autocompletethumbnail and category data. - Alert users to new ticket listings for sold-out events by polling
listings_countandlistingsfromget_event_details. - Discover related artists or teams programmatically via the
altPerformersCarouselreturned byget_performer_events. - Feed a local events widget with geo-inferred upcoming shows using
browse_category_componentswith theDontMissEventsmethod.
| 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 StubHub have an official developer API?+
What does search_autocomplete actually return — does it filter by my query?+
search_events when you need query-matched results grouped by performer, event, and venue entity types.Does the API expose historical sales data or completed transaction prices?+
Can I retrieve tickets for a specific section or filter listings by price within get_event_details?+
get_event_details endpoint returns all active listings for the event without server-side filtering by section or price. Client-side filtering on the returned listings array by section or price fields is the current approach. The venue_map.sectionPopupData object provides per-section pricing summaries if you need aggregated section data without iterating every listing. You can fork the API on Parse and revise the endpoint to add pre-filtered queries if the source supports them.Are venue details like address and seating capacity included in event responses?+
venueName and event date/time fields, but structured venue records with addresses, coordinates, or capacity figures are not currently returned by any endpoint. The API covers ticket listings, performer schedules, and event metadata. You can fork it on Parse and revise to add a venue detail endpoint targeting that data.