/worldafisha/events/search

POST /api/worldafisha/events/search

Price: 10 credits

List WorldAfisha events (Russian-language concerts, theatre, stand-up and shows abroad). Filter by location (country or city slug), period (this weekend, next month) or world region (Europe); with no filter, returns the full upcoming-events listing. Each event has title, performers, category (genre), program, start date and time, city, country, venue, ticket price and currency, external ticket url and image.

How to use it

List WorldAfisha events. Set count to how many you want. Filter by location (country/city slug like 'berlin' or 'ssha'), period (weekend / next_month) or region (europe); with no filter you get all upcoming events. Each item has id, alias, title, performers, category, program, start_at (unix seconds), city, venue, price, currency, ticket_url, image, person_alias and source_url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• location string nullable — Country or city slug to list events in (e.g. 'berlin', 'ssha', 'ispaniya', 'madrid') (examples: "berlin", "ssha")
• period string nullable — Restrict to a time period (one of: "weekend", "next_month")
• region string nullable — Restrict to a world region (one of: "europe")
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "WorldafishaEvent")
• id string nullable
• alias string nullable
• performers array (default: [])
• category string nullable
• program string nullable
• description string nullable
• start_at integer nullable
• city string nullable
• country string nullable
• venue string nullable
• price number nullable
• currency string nullable
• ticket_url string nullable
• image string nullable
• person_alias 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 — 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.

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.