POST /api/interpark/tickets/ranking
Price: 10 credits
Get the Interpark Ticket booking ranking for a genre and period: rank, previous rank, booking share, show dates, venue, artists and booking windows
booking_rate is the show's share of bookings in the genre over the period, in percent. Rows typed @interpark_ranked_sports_game are sports events: interpark/tickets answers them while they are on sale and may stop answering later.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)genre string required — Ranking genre (one of: "musical", "musical_licensed", "musical_original", "concert", "concert_domestic", "concert_indie", "concert_talk", "dance", "sports", "leisure", "exhibition_event", "exhibition", "event", "kids", "kids_musical", "kids_activity", "classic_dance", "classic_opera", "ballet_dance", "traditional_music", "play", "play_limited", "play_steady")period string — Ranking period (default: "daily"; one of: "daily", "weekly", "monthly")count integer required — Max number of shows (min: 1; max: 100)@type string (default: "InterparkRankedShow")id string requiredurl string requiredgoods_key string nullablerank integer nullableprevious_rank integer nullablebooking_rate number nullableperiod_start integer nullableperiod_end integer nullableranking_genre string nullablename string nullablegenre string nullablesub_genre string nullableposter string nullablevenue_code string nullablevenue string nullableregion string nullablestart_date integer nullableend_date integer nullablebooking_opens_at integer nullablebooking_closes_at integer nullablebooking_deadline string nullablecancellation_deadline string nullablemain_artists array (default: [])keywords string nullableseat_type string nullableis_member_discount boolean (default: false)is_safe_booking boolean (default: false)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.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.