/torontovka/events

POST /api/torontovka/events

Price: 1 credit

Get full Torontovka event details by event id, slug or event page URL: title, full description, category, session dates, start and end date, city, venue, address, external ticket url, image and likes.

How to use it

Fetch one Torontovka event by id (e.g. 3887), alias (slug, e.g. 'festival-zhara-2026-3887') or its full event URL. Returns one item with id, alias, title, description, category, start_at, end_at, dates (all session datetimes), city, country, venue, address, ticket_url, has_tickets, is_featured, like_count, dislike_count, image, source_url and lang. Discover events via torontovka/events/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• event string required — Torontovka event id, event slug or event page URL (examples: "3887", "festival-zhara-2026-3887", "https://torontovka.com/afisha/festival-zhara-2026-3887"; minLength: 1)

Response

• @type string (default: "TorontovkaEvent")
• id string required
• alias string nullable
• description string nullable
• category string nullable
• category_id integer nullable
• start_at string nullable
• end_at string nullable
• dates array (default: [])
• city string nullable
• country string (default: "Canada")
• venue string nullable
• address string nullable
• ticket_url string nullable
• has_tickets boolean nullable
• is_featured boolean nullable
• like_count integer nullable
• dislike_count integer nullable
• image string nullable
• source_url string nullable
• lang string (default: "ru")

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 — Event not found (well-formed but nonexistent event id or slug) 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.