/expato/events/search

POST /api/expato/events/search

Price: 20 credits

List and search Expato.nl events (Russian-language concerts, theatre, stand-up, lectures and shows across the Netherlands). Filter by free-text keyword, city, category, event language, status, venue, organizer and promo availability, and order by date. Each event has title, poster image, ticket url, price and currency, start date and time, city, venue, hall, language, categories, description, status and organizer.

How to use it

List Expato.nl events. Set count to how many you want. Optionally filter by keyword, city, category, language, status, venue, organizer or promo_available, and sort by date. Each item has id, alias, title, source_url, image, ticket_url, price, currency, start_at (unix seconds), display_until_at, city, venue, hall, language, categories, description, status, is_active, organizer, organizer_url and country.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Free-text search across event text fields (title, description, location and more)
• city array nullable — Filter by one or more cities (one of: "Алкмаар", "Амстердам", "Гаага", "Гронинген", "Делфт", "Зандам", "Зволле", "Лейден", "Маастрихт", "Наймеген", "Рейсвейк", "Роттердам", "Тилбург", "Утрехт", "Харлем", "Хертогенбос", "Хофддорп", "Эйндховен")
• category array nullable — Filter by one or more categories (one of: "Благотворительность", "Для детей", "Искусство", "История", "Кино", "Лекции", "Литература", "Музыка", "Образование", "Политика", "Презентация книги", "Спектакли", "Творческая встреча", "Фестиваль", "Юмор")
• language array nullable — Filter by one or more event languages (one of: "Английский", "Английский (с русскими субтитрами)", "Белорусский", "Грузинский", "Иврит (с английскими субтитрами)", "Нидерландский", "Русский", "Украинский", "Французский")
• status array nullable — Filter by event status (active / past) (one of: "Активные", "Прошедшие")
• venue string nullable — Filter by venue name or address (substring match)
• organizer string nullable — Filter by organizer name (substring match)
• promo_available boolean nullable — Keep only events that have a promo code
• sort string — Result ordering (default: "default"; one of: "default", "date_asc", "date_desc")
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "ExpatoEvent")
• id string nullable
• alias string nullable
• source_url string nullable
• image string nullable
• images array (default: [])
• ticket_url string nullable
• price number nullable
• currency string nullable
• start_at integer nullable
• display_until_at integer nullable
• city string nullable
• venue string nullable
• hall string nullable
• language string nullable
• categories array (default: [])
• description string nullable
• promo_code string nullable
• has_promo boolean (default: false)
• status string nullable
• is_active boolean (default: false)
• organizer string nullable
• organizer_url string nullable
• country string (default: "Netherlands")
• 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.