/ticketmaster/attractions/events

POST /api/ticketmaster/attractions/events

Price: 1 credit

Get upcoming events (tour schedule) for a Ticketmaster attraction (artist, team, or show) by id or artist page URL. Each item is an event with name, event page URL, start and on-sale dates, timezone, category, partner and availability flags, presale windows, the venue (name, address, city, state, country and coordinates), and the line-up of attractions. Optional start/end date-range filter.

How to use it

Fetch upcoming events for one Ticketmaster attraction by id (e.g. 2436713) or artist URL. Set count to how many events you want. Optional start_date/end_date (YYYY-MM-DD) date-range filter. domain selects the marketplace. Each item has id, name, discovery_id, url, image, start_at, end_at, onsale_at, date_display, span_multiple_days, timezone, category, is_partner, is_sold_out, is_cancelled, is_postponed, is_rescheduled, is_tba, is_virtual, is_local, has_limited_availability, ticketing_status, event_change_status, presales, venue and artists.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• attraction string required — Ticketmaster attraction (artist/team/show) id or artist page URL (examples: "2436713", "https://www.ticketmaster.com/madison-beer-tickets/artist/2436713"; minLength: 1)
• count integer required — Max number of events to return (min: 1)
• start_date string nullable — Only events on or after this date (YYYY-MM-DD) (examples: "2026-09-01")
• end_date string nullable — Only events on or before this date (YYYY-MM-DD) (examples: "2026-10-01")
• domain string — Ticketmaster marketplace domain (default: "ticketmaster.com"; one of: "ticketmaster.com", "ticketmaster.co.uk", "ticketmaster.com.au", "ticketmaster.co.nz", "ticketmaster.ca", "ticketmaster.com.mx", "ticketmaster.com.br", "ticketmaster.cl", "ticketmaster.ie", "ticketmaster.de", "ticketmaster.at", "ticketmaster.ch", "ticketmaster.nl", "ticketmaster.be", "ticketmaster.fr", "ticketmaster.es", "ticketmaster.it", "ticketmaster.pl", "ticketmaster.cz", "ticketmaster.dk", "ticketmaster.no", "ticketmaster.se", "ticketmaster.fi", "ticketmaster.ae", "ticketmaster.co.za", "ticketmaster.co.il", "ticketmaster.sg")

Response

• @type string (default: "TicketmasterEvent")
• id string required
• name string required
• discovery_id string nullable
• url string nullable
• image string nullable
• start_at string nullable
• end_at string nullable
• onsale_at string nullable
• date_display string nullable
• span_multiple_days boolean nullable
• timezone string nullable
• category string nullable
• is_partner boolean nullable
• is_sold_out boolean nullable
• is_cancelled boolean nullable
• is_postponed boolean nullable
• is_rescheduled boolean nullable
• is_tba boolean nullable
• is_virtual boolean nullable
• is_local boolean nullable
• has_limited_availability boolean nullable
• ticketing_status string nullable
• event_change_status string nullable
• presales array (default: [])
  • @type string (default: "TicketmasterPresale")
  • name string nullable
  • start_at string nullable
  • end_at string nullable
• venue object nullable
  • @type string (default: "TicketmasterEventVenue")
  • id string nullable
  • name string nullable
  • city string nullable
  • state string nullable
  • country string nullable
  • country_code string nullable
  • address string nullable
  • postal_code string nullable
  • latitude number nullable
  • longitude number nullable
  • url string nullable
  • image string nullable
• artists array (default: [])
  • @type string (default: "TicketmasterEventArtist")
  • id string nullable
  • name string nullable
  • url string nullable
  • image string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.