Ticketmaster APIticketmaster.nl ↗
Search Ticketmaster Netherlands events, get event details, resale listings, and venue seating manifests via a structured JSON API. 4 endpoints.
What is the Ticketmaster API?
The Ticketmaster Netherlands API provides 4 endpoints to search live events, retrieve detailed event metadata, fetch verified resale ticket listings, and access venue seating manifests from ticketmaster.nl. The search_events endpoint accepts a keyword query and returns up to 20 matching events per call, including IDs, dates, venue details, artist associations, and availability flags — giving developers a direct path into the Dutch ticketing catalog.
curl -X GET 'https://api.parse.bot/scraper/53da0afb-f851-46f8-b3be-060e8b0b028c/search_events?query=concert' \ -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-nl-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.
"""Ticketmaster NL: search events, get details, explore venue layouts."""
from parse_apis.ticketmaster_nl_api import TicketmasterNL, EventNotFound
client = TicketmasterNL()
# Search for concert events — limit caps total items fetched
for event in client.eventsummaries.search(query="concert", limit=5):
print(event.name, event.city, event.date)
# Drill into the first result's full details
summary = client.eventsummaries.search(query="Amsterdam", limit=1).first()
if summary:
detail = summary.details()
print(detail.name, detail.venue.name, detail.venue.city)
print(detail.ticket_limit, detail.currency_code, detail.sold_out)
# Walk venue seating sections via sub-resource
if detail.has_sections:
for section in detail.manifest.list(limit=5):
print(section.code, section.name)
# Direct event lookup by ID with typed error handling
try:
event = client.events.get(event_id="1432752632")
print(event.name, event.canonical_url)
except EventNotFound as exc:
print(f"Event not found: {exc.event_id}")
print("exercised: eventsummaries.search / details / events.get / manifest.list")
Search for events on ticketmaster.nl using a keyword. Returns up to 20 events per request with their IDs, names, dates, venues, and availability status. The total field indicates the number of matching events server-side.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword (e.g., 'concert', 'festival', 'Amsterdam') |
{
"type": "object",
"fields": {
"total": "integer total number of matching events across all pages",
"events": "array of event objects with id, name, date, venue, city, country, url, sold_out, cancelled, artists"
},
"sample": {
"data": {
"total": 10000,
"events": [
{
"id": "1432752632",
"url": "https://www.ticketmaster.nl/event/twilight-in-concert-tickets/1432752632",
"city": "Eindhoven",
"date": "2026-10-20T18:15:00Z",
"name": "Twilight In Concert",
"venue": "Muziekgebouw Eindhoven",
"artists": [
"Twilight In Concert"
],
"country": "NL",
"sold_out": false,
"cancelled": false
}
]
},
"status": "success"
}
}About the Ticketmaster API
Event Discovery and Details
The search_events endpoint takes a single query string — a keyword like 'amsterdam', 'festival', or an artist name — and returns an array of event objects. Each object includes a unique id, name, date, venue, city, country, url, sold_out boolean, cancelled boolean, and associated artists. The total field reflects the full server-side count of matching events, so you can track how many results exist beyond the 20 returned per call. Feed those IDs into get_event_details to pull richer metadata: venue coordinates (latitude, longitude), ticket_limit, currency_code, sub_category, and a canonical_url pointing back to the event page on ticketmaster.nl.
Resale Listings and Seating Manifests
get_resale_listings accepts an event_id and returns verified resale ticket listings for that event, including price, seat location where available, and seller information. The total_resale field tells you how many resale listings exist. For venues with defined seating sections, get_event_manifest returns the layout as arrays of levels and sections, each with a code and name. Events where has_sections is false in the get_event_details response will return stale_input from the manifest endpoint — check that flag before calling it.
Pagination and ID Chaining
The search endpoint does not expose a pagination parameter in its current form; each call returns up to 20 events and a total count. Event IDs from search_events are the primary key for all other endpoints. Passing a non-existent event_id to get_event_details or get_event_manifest returns stale_input rather than a 404, so consumers should validate the ID against search results before chaining calls.
The Ticketmaster API is a managed, monitored endpoint for ticketmaster.nl — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ticketmaster.nl 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.nl 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 and festivals in the Netherlands by querying
search_eventswith city or genre keywords. - Monitor ticket availability and sold-out status across multiple events using the
sold_outandcancelledfields fromsearch_events. - Build a resale price tracker by polling
get_resale_listingsfor specific event IDs and recording price changes over time. - Render an interactive seating map by combining
has_sectionsfromget_event_detailswith section and level data fromget_event_manifest. - Enforce per-order ticket limits in a booking assistant by reading the
ticket_limitfield fromget_event_details. - Geocode venue locations for a map-based event discovery UI using
latitudeandlongitudereturned byget_event_details. - Filter events by sub-category (e.g., comedy, classical) using the
sub_categoryobject available in detailed event responses.
| 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 have an official developer API?+
What does `get_event_manifest` return, and when should I skip calling it?+
get_event_manifest returns levels and sections arrays, each containing a code and name per entry, representing the physical seating layout of the venue. Before calling it, check the has_sections field in get_event_details: if it is false, the event has no section data and the manifest endpoint will return stale_input instead of a layout.Does the search endpoint support pagination to retrieve more than 20 events?+
search_events endpoint returns up to 20 events per call and exposes a total count but does not accept a page or offset parameter. You can fork this API on Parse and revise it to add a pagination input if your use case requires scrolling through larger result sets.Does the API cover ticket price tiers or category-level pricing for primary sales?+
get_resale_listings endpoint for resale tickets. Primary sale ticket prices and category breakdowns are not exposed. You can fork this API on Parse and revise it to add an endpoint targeting primary ticket category pricing.Is there a known quirk when passing event IDs from outside the search results?+
get_event_details and get_event_manifest return stale_input rather than an error when an event ID does not exist or is no longer valid. Always source event_id values from current search_events results to avoid silent failures in downstream logic.