Ticketmaster APIticketmaster.com.mx ↗
Search and retrieve event data from ticketmaster.com.mx. Get concerts, sports, theater, and family events across Mexico with venue, date, and artist details.
What is the Ticketmaster API?
The Ticketmaster Mexico API exposes 3 endpoints for searching and retrieving event listings from ticketmaster.com.mx, covering concerts, sports, theater, and family events across Mexico. The search_events endpoint accepts keyword, region, sort order, and pagination parameters, returning event arrays with titles, dates, venue details, artist lineups, and availability status. A companion get_event_details endpoint delivers full per-event records by Ticketmaster event ID.
curl -X GET 'https://api.parse.bot/scraper/95ab3ad7-5151-47ef-99b3-ad404d90f541/search_events?page=1&sort=date&query=concert®ion=802' \ -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-com-mx-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: TicketmasterMX SDK — search events, drill into details, list regions."""
from parse_apis.ticketmaster_mexico_api import TicketmasterMX, Sort, Region, EventNotFound
client = TicketmasterMX()
# List available regions for filtering
for region in client.regionmappings.list(limit=4):
print(region.code, region.name)
# Search for rock events in Mexico City, sorted by relevance
for event in client.events.search(query="rock", region=Region.MEXICO_CITY, sort=Sort.RELEVANCE, limit=5):
print(event.title, event.id, event.sold_out, event.cancelled)
print(event.venue.name, event.venue.city, event.venue.country_name)
print(event.dates.start_date, event.dates.date_display)
# Drill into a single event's full details
first_event = client.events.search(query="concert", sort=Sort.DATE, limit=1).first()
if first_event:
try:
detail = first_event.details(event_name=first_event.title)
print(detail.source, detail.event.title, detail.event.venue.name)
except EventNotFound as exc:
print(f"Event not found: {exc.event_id}")
# Construct an event directly by ID and fetch details
event = client.event(id="4318758")
detail = event.details(event_name="UNE MINUTE DE SILENCE")
print(detail.source, detail.event.title)
print("exercised: regionmappings.list / events.search / event.details")
Full-text search over Ticketmaster Mexico's global event catalog. `query` matches event titles and artist names; `sort` orders by date or relevance. Results span worldwide Ticketmaster inventory accessible from the .mx portal. Paginates via integer page number. Each event includes venue details, artist lineup, date information, and ticket availability status.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (1-indexed) |
| sort | string | Sort order for results |
| query | string | Search keyword (e.g. artist name, event name, genre) |
| region | string | Region code for filtering events by location |
{
"type": "object",
"fields": {
"total": "integer total number of matching events",
"events": "array of event objects with title, id, dates, venue, artists, and status fields",
"singleVenue": "boolean indicating if all results are at a single venue"
},
"sample": {
"data": {
"total": 10000,
"events": [
{
"id": "4318754",
"url": "https://www.ticketmaster.fr/fr/manifestation/une-minute-de-silence-billet/idmanif/656773/idtier/18864121",
"dates": {
"startDate": "2026-06-10T18:00:00Z",
"onsaleDate": "2026-04-16T14:42:00Z",
"dateDisplay": "showDateTime",
"spanMultipleDays": false
},
"title": "UNE MINUTE DE SILENCE",
"venue": {
"city": "Lyon",
"name": "THEATRE COMEDIE ODEON",
"country": "FR",
"countryCode": "FR",
"countryName": "France"
},
"artists": [],
"soldOut": false,
"cancelled": false,
"postponed": false,
"discoveryId": "ZkyMmBwZ1A7Gbqf"
}
],
"singleVenue": false
},
"status": "success"
}
}About the Ticketmaster API
Endpoints and Data Returned
The search_events endpoint is the primary discovery surface. Pass a query string (artist name, genre, or event title), a region code, a sort value (date or relevance), and a page number to page through results. The response includes a total count of matching events, a boolean singleVenue flag, and an events array where each object carries the event's title, id, dates, venue, artists, and status.
Region Filtering
Four region codes are supported: 801 (Todo México), 802 (Ciudad de México), 803 (Monterrey), and 804 (Guadalajara). These codes are returned directly by the get_regions endpoint, which requires no parameters and returns a static key-value map. Passing 801 to search_events returns results across all of Mexico without geographic restriction.
Event Detail Lookup
get_event_details accepts an event_id (e.g. 3D00639FB2C115CB) and an event_name string. The event_name parameter is required for reliable results: if the event's page is access-protected, the endpoint falls back to locating the event through search results. The response includes the full event object — title, id, dates, venue, artists, status, and url — plus a source field indicating whether data came from the event page directly (event_page) or via the search fallback (search_results).
Coverage and Pagination
All event categories listed on ticketmaster.com.mx are in scope: music, sports, arts and theater, and family events. Pagination in search_events is 1-indexed via the page parameter. The total field in the response lets callers calculate how many pages are available for a given query.
The Ticketmaster API is a managed, monitored endpoint for ticketmaster.com.mx — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ticketmaster.com.mx 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.com.mx 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 an event calendar app scoped to Ciudad de México using the
802region code and date sort. - Monitor upcoming concerts for a specific artist by querying the artist name and tracking
statuschanges across poll cycles. - Aggregate venue schedules by filtering
search_eventsresults on thevenuefield across multiple region codes. - Create a cross-genre event discovery feed for Mexico City by paginating through
search_eventswith no keyword filter. - Enrich a ticketing recommendation engine with artist lineup data from the
artistsfield in event detail responses. - Track event availability for sold-out alerts by polling
get_event_detailsfor specific event IDs and checking thestatusfield. - Build a Monterrey-specific events widget using region code
803filtered by event category keywords.
| 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 the `source` field in `get_event_details` indicate?+
event_page means the data came directly from the event's own page. A value of search_results means the event page was access-protected and the endpoint found the record through a search fallback using the event_name parameter. This distinction matters when you need to know whether all detail fields are fully populated.Does the API return ticket pricing or purchase URLs?+
status and a direct url field per event, but no ticket price tiers, fee breakdowns, or transactional purchase data. You can fork this API on Parse and revise it to add an endpoint targeting ticket pricing sections of individual event pages.Are regions beyond Ciudad de México, Monterrey, and Guadalajara supported?+
801 (Todo México), 802 (Ciudad de México), 803 (Monterrey), and 804 (Guadalajara), as returned by get_regions. Events in other Mexican cities are reachable via the 801 code but cannot be isolated by city. You can fork this API on Parse and revise it to add finer-grained regional codes if ticketmaster.com.mx exposes them.Is there a way to filter events by category (e.g. only sports or only theater)?+
search_events endpoint does not expose a dedicated category parameter. Category filtering can be approximated by passing genre or category terms as the query value. The API covers concerts, sports, theater, and family events in the same result pool. You can fork this API on Parse and revise it to add a category filter parameter if the source supports category-scoped queries.