POST /api/ticketmaster/attractions/related
Price: 10 credits
Get related Ticketmaster attractions ('fans also viewed') for an attraction by id or artist page URL. Each item is a related attraction with its id, name, artist page URL and image.
Fetch related attractions (fans also viewed) for one Ticketmaster attraction by id (e.g. 1094215) or artist URL. Set count to how many you want. domain selects the marketplace. Each item has id, name, url and image.
access-token string requiredtimeout 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)count integer required — Max number of related attractions to return (min: 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")@type string (default: "TicketmasterRelatedAttraction")id string nullablename string nullableurl string nullableimage string nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.