/ticketmaster/attractions

POST /api/ticketmaster/attractions

Price: 10 credits

Get full Ticketmaster attraction details (artist, team, or show) by id or artist page URL: name, description, category and genre, act type (Group/Individual) and sub type (Band/Musician), image and cover banner, average fan rating and review count, upcoming event count, biography, setlists (with song lists), FAQs, media gallery, related news articles, and related attractions ('fans also viewed').

How to use it

Fetch a single Ticketmaster attraction (artist/team/show) by id (e.g. 1094215) or artist URL. domain selects the marketplace. Returns one item with id, name, url, image, cover, description (short blurb), category, genre, sub_genre, attraction_type (Group/Individual), attraction_sub_type (Band/Musician/…), discovery_id, references (external ids), has_video, rating, review_count, upcoming_event_count, bio (long biography), setlists (tour_name, venue_name, city_name, country_name, event_date, songs), faqs (question, answer), gallery (document_title, image, video_url), news (document_title, text, url, image) and related attractions (id, name, url, image).

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: "1094215", "https://www.ticketmaster.com/taylor-swift-tickets/artist/1094215"; 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: "TicketmasterAttraction")
• id string required
• name string required
• url string nullable
• image string nullable
• cover string nullable
• category string nullable
• genre string nullable
• sub_genre string nullable
• attraction_type string nullable
• attraction_sub_type string nullable
• discovery_id string nullable
• references object (default: {})
  • * string
• has_video boolean nullable
• rating number nullable
• review_count integer nullable
• upcoming_event_count integer nullable
• description string nullable
• bio string nullable
• setlists array (default: [])
  • @type string (default: "TicketmasterSetlist")
  • tour_name string nullable
  • venue_name string nullable
  • city_name string nullable
  • country_name string nullable
  • event_date string nullable
  • songs array (default: [])
• faqs array (default: [])
  • @type string (default: "TicketmasterFaq")
  • question string nullable
  • answer string nullable
• gallery array (default: [])
  • @type string (default: "TicketmasterGalleryItem")
  • document_title string nullable
  • image string nullable
  • video_url string nullable
• news array (default: [])
  • @type string (default: "TicketmasterNews")
  • document_title string nullable
  • text string nullable
  • url string nullable
  • image string nullable
• related array (default: [])
  • @type string (default: "TicketmasterRelatedAttraction")
  • 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 — Attraction not found (well-formed but nonexistent attraction 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.