/interpark/tickets/schedules

POST /api/interpark/tickets/schedules

Price: 20 credits

List the performances of an Interpark Ticket show by code or URL within a date range: start time, sale and cancellation windows, and optionally seats left per grade and the cast of each performance

How to use it

Without dates the whole run of the show is listed. include_seats adds remaining seats and the cast per performance.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• ticket string required — Interpark Ticket show code, show URL or goods key (examples: "26011520", "https://nol.yanolja.com/ticket/products/26011520", "26011520:23000860"; minLength: 1)
• date_from integer nullable — Earliest performance date, unix seconds (min: 0)
• date_to integer nullable — Latest performance date, unix seconds (min: 0)
• include_seats boolean — Add seats left per grade and the cast of each performance (default: false)
• count integer required — Max number of performances (min: 1; max: 500)

Response

• @type string (default: "InterparkPerformance")
• id string required
• ticket_id string required
• sequence string required
• starts_at integer nullable
• day_of_week string nullable
• sale_opens_at integer nullable
• sale_closes_at integer nullable
• cancellation_closes_at integer nullable
• online_sale_closes_on integer nullable
• casting_opens_at integer nullable
• seats_left array (default: [])
  • @type string (default: "InterparkSeatsLeft")
  • seat_grade string nullable
  • remaining integer nullable
• cast array (default: [])
  • @type string (default: "InterparkPerformer")
  • actor_id string nullable
  • actor_name 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 — No Interpark show under that code 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.