/zimamagazine/events/search

POST /api/zimamagazine/events/search

Price: 20 credits

Search the ZIMA Magazine events listing — Russian-language cultural events (concerts, theatre, exhibitions, festivals, cinema, public meetings and more) across the UK, Europe, the UAE and beyond. Combine a keyword with filters for country, category, city and date range. Returns event cards with title, description, image, country, city, venue, address, start and end date, ticket link and categories.

How to use it

Search ZIMA Magazine events (Russian-language cultural events worldwide). Set count to how many results you want; id is usable with zimamagazine/events. Filter by country, category, city (substring match) and a date_from/date_to range; city is comma-separated when the event runs in several cities. By default only currently active and upcoming events are returned; set include_past to also include events that have already finished. All events are in Russian.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string — Search keyword (default: ""; examples: "джаз", "выставка", "концерт")
• count integer required — Max number of results to return (min: 1)
• country string nullable — Filter by country (one of: "Великобритания", "Франция", "Германия", "Кипр", "Испания", "Италия", "Нидерланды", "ОАЭ", "Израиль", "Австрия", "Швейцария", "Другая")
• category string nullable — Filter by event category (one of: "Концерты", "Театр", "Выставки", "Публичные встречи", "Фестивали", "Прогулки и поездки", "Кино", "Для детей", "Гастрономия")
• city string nullable — Filter by city name (examples: "Лондон", "Берлин")
• date_from string nullable — Only events active on or after this date (YYYY-MM-DD) (examples: "2026-07-01")
• date_to string nullable — Only events starting on or before this date (YYYY-MM-DD) (examples: "2026-07-31")
• include_past boolean — Include events that have already finished (default: false)

Response

• @type string (default: "ZimamagazineEvent")
• id string required
• alias string nullable
• title string required
• description string nullable
• image string nullable
• country string nullable
• city string nullable
• venue string nullable
• address string nullable
• start_date string nullable
• end_date string nullable
• updated_at string nullable
• ticket_url string nullable
• categories array (default: [])
• is_zima_event boolean (default: false)
• 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.