Ticketmaster APIticketmaster.de ↗
Access Ticketmaster.de event search, venue details, attraction profiles, and category navigation via 6 structured API endpoints.
What is the Ticketmaster API?
The Ticketmaster Germany API exposes 6 endpoints covering event search, attraction profiles, venue details, autocomplete suggestions, and site navigation categories for ticketmaster.de. The search_events endpoint returns paginated results with event titles, dates, artists, venue references, and ticket URLs, while get_attraction_details provides artist synopses, category classifications, and recent setlist data — all in structured JSON.
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'
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 ticketmaster-de-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.
"""Walkthrough: Ticketmaster Germany SDK — event discovery, artist details, venue lookup."""
from parse_apis.ticketmaster_germany_api import Ticketmaster, ResourceNotFound
client = Ticketmaster()
# Search for rock events — limit caps total items fetched across pages
for event in client.searchresults.search(query="rock", limit=3):
print(event.title, event.venue.city, event.dates.start_date)
# Drill into the first result's artist via suggestions
suggestion = client.suggestionlists.search(keyword="rock", limit=1).first()
if suggestion:
print(suggestion.title, suggestion.category, suggestion.url)
# Look up full attraction details by ID
try:
artist = client.attractions.get(attraction_id="390223")
print(artist.name, artist.major_category.name if artist.major_category else "")
except ResourceNotFound as exc:
print(f"Artist not found: {exc}")
# Look up a venue by ID and code
venue = client.venues.get(venue_id="715", venue_code="hanfaustse")
print(venue.name, venue.address.city, venue.location.latitude)
# Browse the menu config for categories and cities
config = client.menuconfigs.get()
for cat in config.categories:
print(cat.name, cat.url)
print("exercised: searchresults.search / suggestionlists.search / attractions.get / venues.get / menuconfigs.get")
Full-text search over Ticketmaster Germany events. Returns a paginated list of matching events plus top search suggestions for related artists/venues. Each event includes title, dates, venue, artists, and ticket URL. The total field reports the server-side match count (capped at 10000).
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-based) |
| queryrequired | string | Search keyword for events (artist name, genre, city, or event title) |
{
"type": "object",
"fields": {
"page": "integer current page number",
"total": "integer total number of matching events (capped at 10000)",
"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"
},
"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 Discovery
The search_events endpoint accepts a query string (artist name, genre, city, or event title) and an optional page parameter for 1-based pagination. Each event object in the response includes a title, ID, date fields, venue reference, associated artists, direct ticket URL, and status flags. A total field reports the server-side match count, capped at 10,000. The response also contains a suggestions array of related artists and venues matching the query, each with an ID, title, URL, image, and category label — useful for refining searches or feeding into detail endpoints.
Artist and Venue Detail
The get_attraction_details endpoint takes a numeric attraction_id (found in artist URLs from search results) and returns the artist name, an HTML-formatted synopsis, majorCategory and minorCategory classification objects, an image URL, and a setlistInfo object containing recent setlists and the artist's profile URL. The get_venue_details endpoint requires both a numeric venue_id and a venue_code slug, and returns the venue name, structured address (line1, city, postalCode, country), geographic coordinates (longitude and latitude), a timezone string such as Europe/Berlin, seat map image URLs, and generalInfoBlocks with HTML sections for directions, parking, and public transit.
Autocomplete and Navigation
The find_suggest endpoint accepts a keyword and returns up to 10 matching attraction or venue objects, each with an ID, title, result count, URL, image, and category. This is the recommended way to discover attraction IDs before calling get_attraction_details. The get_menu_config endpoint requires no inputs and returns the full site navigation structure: an array of city objects with names and URLs, and a categories array where each entry includes an ID, name, URL, subCategories, and popularSubCategories — covering the full browse taxonomy used on ticketmaster.de.
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?+
- Aggregate upcoming concerts in a specific German city by querying
search_eventswith a city name and reading venue and date fields. - Build an artist discovery tool using
find_suggestautocomplete to resolve artist names to numeric IDs before fetching full profiles viaget_attraction_details. - Display venue information pages with address, coordinates, seat maps, and transit directions sourced from
get_venue_details. - Populate event category navigation by reading the
categoriesandsubCategoriesarrays returned byget_menu_config. - Track which artists have recent setlist data by checking the
setlistInfofield in attraction detail responses. - Build a concert calendar by paginating
search_eventsresults and grouping events by thedatesfield. - Surface top artist and venue suggestions alongside search results using the
suggestionsarray fromsearch_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 | 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 Ticketmaster Germany offer an official developer API?+
What does the `search_events` endpoint return for the `total` field, and how reliable is it for pagination?+
total field reflects the server-reported match count for the query and is capped at 10,000 regardless of the actual number of results. You can paginate using the page parameter (1-based), but results beyond the cap are not addressable. For queries with very broad terms (e.g., a major genre), the capped total may underrepresent the true result set.Does the API return ticket prices or availability status?+
Can I look up events by category or genre without a keyword search?+
get_menu_config endpoint returns category IDs, names, and URLs for the full site taxonomy, and search_events accepts genre or category terms as the query string. You can fork this API on Parse and revise it to add a category-browse endpoint using the category IDs from get_menu_config.What inputs does `get_venue_details` require, and where do I find them?+
venue_id (the last path segment of a venue URL, e.g., '715') and a venue_code slug (the second-to-last path segment, e.g., 'hanfaustse'). Both values appear in venue URLs returned within event objects from search_events or suggestions from find_suggest.