Ticketmaster APIticketmaster.de ↗
Search events, get artist and venue details, autocomplete suggestions, and browse categories on Ticketmaster Germany via 5 structured API endpoints.
What is the Ticketmaster API?
The Ticketmaster Germany API covers 5 endpoints that expose event listings, artist profiles, venue details, and site navigation data from ticketmaster.de. Using search_events, you can run full-text queries across all German events or pull the full schedule for a specific attraction by ID, getting back paginated results with dates, venue info, artist references, and availability status flags.
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'
Full-text search over Ticketmaster Germany events, or the event list of one specific artist/attraction. Returns a paginated list of events (20 per page) plus, in keyword mode, top search suggestions for related artists/venues. Each event includes title, dates, venue, artists, and ticket URL. Two modes: supplying only a keyword (query) searches all events and the total field reports the server-side match count (capped at 10000); supplying attraction_id restricts the result to events of that artist/attraction (including international dates), total is the exact count for that artist, suggestions is an empty array, and the keyword is not applied upstream so query is ignored. At least one of query or attraction_id is required; a well-formed attraction_id with no events yields a valid empty result. One upstream request per call.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-based), 20 events per page in both modes |
| query | string | Search keyword for events (artist name, genre, city, or event title). Required unless attraction_id is supplied; ignored when attraction_id is supplied. |
| attraction_id | string | Numeric attraction/artist ID found in artist URLs from search results (e.g. '390223'). When supplied, only events of this artist/attraction are returned (the same ID accepted by get_attraction_details and the last path segment of suggestion and artist urls). |
{
"type": "object",
"fields": {
"page": "integer current page number",
"total": "integer total number of matching events (capped at 10000 in keyword mode; exact artist event count when attraction_id is supplied)",
"events": "array of event objects with title, id, dates, venue, artists, url, and status flags",
"suggestions": "array of suggested artists/venues matching the query with id, title, url, image, category (always empty when attraction_id is supplied)"
},
"sample": {
"data": {
"page": 1,
"total": 10000,
"events": [
{
"id": "120898075",
"url": "https://www.ticketmaster.de/event/set-it-off-europe-summer-2026-tickets/120898075",
"dates": {
"startDate": "2026-06-15T18:00:00Z",
"onsaleDate": "2026-02-26T09:00:00Z"
},
"title": "Set It Off - Europe Summer 2026",
"venue": {
"city": "Hannover",
"name": "Faust (60er Jahre Halle)",
"country": "DE"
},
"artists": [
{
"url": "https://www.ticketmaster.de/artist/set-it-off-tickets/390223",
"name": "Set It Off"
}
],
"soldOut": false
}
],
"suggestions": [
{
"id": "dataAdmin-attraction-00000000005c3be4",
"url": "https://www.ticketmaster.de/artist/rock-legends-tickets/998970",
"image": "https://s1.ticketm.net/dam/a/855/01979862-466f-4796-b97b-aa881037b855_CUSTOM.jpg",
"title": "Rock Legends",
"category": "Rock"
}
]
},
"status": "success"
}
}About the Ticketmaster API
Event Search and Artist Schedules
The search_events endpoint accepts either a free-text query (artist name, city, genre, or event title) or an attraction_id to list all upcoming events for a specific performer. Results are paginated at 20 events per page using the page parameter. Each event object includes title, id, dates, venue, artists, url, and status flags. In keyword mode, the response also includes a suggestions array of related artists and venues with their IDs, images, and category labels — useful for chaining calls to get_attraction_details.
Artist and Venue Details
get_attraction_details takes a numeric attraction_id and returns the artist's name, an HTML-formatted synopsis, majorCategory and minorCategory classification objects, an imageUrl, and a setlistInfo object containing recent setlists and the artist's URL. get_venue_details requires both a numeric venue_id and a venue_code slug (both found in venue URLs), and returns the venue's address, geographic location coordinates, timeZone, seatMaps with image URLs, and generalInfoBlocks containing HTML sections for directions, parking, and public transit.
Discovery and Navigation
find_suggest provides autocomplete results for up to 10 matching artists or venues given a partial keyword, returning each match's id, title, count, url, image, and category. This is the fastest way to resolve an attraction ID before calling other endpoints. get_menu_config requires no inputs and returns the full site category tree — each category with its id, name, url, subCategories, and popularSubCategories — plus a cities array of featured city pages, useful for building navigation or category-filtered browsing.
The Ticketmaster API is a managed, monitored endpoint for ticketmaster.de — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ticketmaster.de 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 ticketmaster.de 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?+
- Build a concert calendar for Germany by paginating through search_events filtered by city or genre keyword.
- Display a touring artist's full German schedule by passing their attraction_id to search_events.
- Render artist profile pages using the name, synopsis, imageUrl, and setlistInfo from get_attraction_details.
- Show venue information including address, coordinates, parking directions, and seat maps from get_venue_details.
- Implement a search autocomplete widget using the find_suggest endpoint with partial artist or venue names.
- Enumerate all event categories and subcategories from get_menu_config to build a site navigation or filter UI.
- Discover attraction IDs for lesser-known acts by using find_suggest before calling get_attraction_details.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.