ticketmaster.de APIticketmaster.de ↗
Access Ticketmaster.de event listings, attraction profiles, venue details, and category navigation via a structured REST API with 6 endpoints.
curl -X GET 'https://api.parse.bot/scraper/1290267d-f9b7-4926-86a8-585f1a8d624b/search_events?page=1&query=rock' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for events on Ticketmaster Germany. Returns a paginated list of events matching the query along with top search suggestions for related artists/venues.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination |
| queryrequired | string | Search keyword (e.g. 'rock', 'berlin', 'Tori Amos') |
{
"type": "object",
"fields": {
"page": "integer current page number",
"total": "integer total number of matching events",
"events": "array of event objects with title, id, dates, venue, artists, and url",
"suggestions": "array of suggested artists/venues matching the query"
},
"sample": {
"data": {
"page": 1,
"total": 39392,
"events": [
{
"id": "680986289",
"url": "https://www.ticketmaster.de/event/tape-head--noni-nicht-ins-leben-verliebt-tour-2026-tickets/680986289",
"dates": {
"startDate": "2026-05-08T18:00:00Z",
"onsaleDate": "2025-09-26T09:00:00Z"
},
"title": "Tape Head & NONI - nicht ins leben verliebt tour 2026",
"venue": {
"city": "Berlin",
"name": "Privatclub",
"country": "DE"
},
"artists": [
{
"url": "https://www.ticketmaster.de/artist/tape-head-noni-tickets/1363584",
"name": "Tape Head & NONI"
}
]
}
],
"suggestions": [
{
"id": "dataAdmin-attraction-00000000005c3be4",
"url": "https://www.ticketmaster.de/artist/rock-legends-tickets/998970",
"title": "Rock Legends",
"category": "Rock"
}
]
},
"status": "success"
}
}About the ticketmaster.de API
The Ticketmaster Germany API covers 6 endpoints for querying live events, artists, and venues on ticketmaster.de. Starting with search_events, you can retrieve paginated event results including titles, dates, venue metadata, and linked artists — all scoped to the German market. Separate endpoints expose full attraction profiles, venue coordinates, autocomplete suggestions, and the site's category/city navigation tree.
Event Search and Details
The search_events endpoint accepts a query string (artist name, city, genre, etc.) and an optional page integer for pagination. Each response includes a total count of matching events plus an events array where each item carries a title, id, dates object, venue reference, artists array, and a direct url. A suggestions array is also returned, surfacing matching artist and venue autocomplete hits alongside the main results.
For a single event, get_event_details accepts either an event_id or a full event_url and returns the name, dates, venue, and artists fields for that record. Note the endpoint documentation flags that some events return limited data.
Attractions and Venues
get_attraction_details resolves a numeric attraction_id to a full profile: name, imageUrl, an HTML-formatted synopsis, and both majorCategory and minorCategory objects (each with name and id). This is useful for enriching event listings with artist biography text and classification data.
get_venue_details requires both a numeric venue_id and a venue_code slug — both of which are available from event search results. The response includes a structured address (line1, city, postalCode, country), a location object with longitude and latitude, and a timeZone string.
Suggestions and Navigation
find_suggest takes a keyword and returns a ranked list of matching attractions and venues, each with an id, title, url, image, and category. This mirrors the site's live autocomplete behavior and is suitable for building search-as-you-type interfaces.
get_menu_config requires no inputs and returns the full navigation structure: a cities array (name + url) and a categories array where each category carries an id, name, url, subCategories, and popularSubCategories. This endpoint is the right source for building category browsers or city-filtered event listings.
- Build a concert discovery app filtered by German cities using
get_menu_configcity slugs andsearch_eventsqueries. - Enrich event pages with artist biographies and images by calling
get_attraction_detailswith IDs from event search results. - Plot venue locations on a map using the
longitudeandlatitudefields fromget_venue_details. - Implement search-as-you-type for artists and venues using the
find_suggestendpoint with a livekeywordinput. - Monitor event availability and total result counts for specific artists by polling
search_eventswith pagination. - Populate a category navigation UI with genre trees and subcategories from
get_menu_config. - Cross-reference event artist IDs with
get_attraction_detailsto retrieve category classifications for genre-based filtering.
| 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 Ticketmaster have an official developer API?+
What does `get_event_details` return, and when does it return limited data?+
name, dates, venue, and artists for the requested event. Some events surface reduced fields — for example, the artists array or detailed dates sub-fields may be absent depending on the event record. Using event_url instead of event_id is an alternative input path if you have the URL from search results but not a parsed ID.Does the API cover ticket pricing or seat availability?+
How does pagination work in `search_events`?+
page integer (the current page) and a total integer (total matching events). Pass an incremented page parameter to step through results. Page size is fixed by the source — the response does not expose a configurable pageSize field.