/ticketmaster/venues

POST /api/ticketmaster/venues

Price: 10 credits

Get full Ticketmaster venue details by id or venue page URL: name, address, city, state, postal code, country and coordinates, image, timezone, box office / parking / accessibility / rules info blocks, seating chart images, city category links, related venue links, and the upcoming event count.

How to use it

Fetch a single Ticketmaster venue by id (e.g. 483329) or venue URL. domain selects the marketplace. Returns one item with id, name, url, image, timezone, discovery_id, references, address, city, state, postal_code, country, latitude, longitude, general_info (box office/parking/accessibility/rules as a title->text map), city_categories, related_links, seat_maps (name, image) and upcoming_event_count.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• venue string required — Ticketmaster venue id or venue page URL (examples: "483329", "https://www.ticketmaster.com/madison-square-garden-tickets-new-york/venue/483329"; minLength: 1)
• 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: "TicketmasterVenue")
• id string required
• name string required
• url string nullable
• image string nullable
• timezone string nullable
• discovery_id string nullable
• references object (default: {})
  • * string
• address string nullable
• city string nullable
• state string nullable
• postal_code string nullable
• country string nullable
• latitude number nullable
• longitude number nullable
• general_info object (default: {})
  • * string
• city_categories array (default: [])
  • @type string (default: "TicketmasterVenueCategory")
  • id string nullable
  • name string nullable
  • url string nullable
• related_links array (default: [])
  • @type string (default: "TicketmasterVenueRelatedLink")
  • document_title string nullable
  • url string nullable
  • image string nullable
• seat_maps array (default: [])
  • @type string (default: "TicketmasterVenueSeatMap")
  • name string nullable
  • image string nullable
• upcoming_event_count integer 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 — Venue not found (well-formed but nonexistent venue id) 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.