/afishafi/events/search

POST /api/afishafi/events/search

Price: 20 credits

Search Afisha.fi events (Russian-language cultural events across Finland). Provide a keyword for a full-text search over all events, or filter the upcoming listing by category, city and date range. Each item is a full event with title, description, start and end dates, city, organizer, price and currency, ticket link, images and view count.

How to use it

Search Afisha.fi events. Two modes: provide keyword for a full-text search across all events (past and upcoming), or omit keyword and filter the upcoming listing by category, city and start_date/end_date (YYYY-MM-DD). Keyword search does not combine with category/city/date filters. Set count to how many results you want. Each item has id, title, description, start_at/end_at, city, organizer, price, currency (EUR), ticket_url, images, view_count, source_url and lang.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Full-text search query across all events (past and upcoming) (examples: "концерт", "балет")
• category string nullable — Filter the listing by a single event category (one of: "ballet", "concerts", "clubs", "exhibitions", "theatre", "kids", "seminars", "youth", "excursions")
• city string nullable — Filter the listing by a single Finnish city (one of: "vaasa", "valkeala", "vantaa", "varkaus", "vesanto", "vihti", "vuokatti", "ivalo", "ilomantsi", "imatra", "joensuu", "kajaani", "kangasala", "kankaanpaa", "karjaa", "karkkila", "kemi", "kerava", "keuruu", "kirkkonummi", "kittila", "kokkola", "kotka", "kouvola", "kristiinankaupunki", "kuopio", "lapinlahti", "lappeenranta", "lapua", "lahti", "levi", "leppavirta", "lieksa", "loviisa", "lohja", "lviv", "mikkeli", "nastola", "nummi_pusula", "nurmijarvi", "orimattila", "oulu", "paimio", "parikkala", "pieksamaki", "pietarsaari", "porvoo", "pori", "posio", "pyha", "raasepori", "raahe", "rauma", "riihimaki", "rovaniemi", "ruka", "savonlinna", "salla", "salo", "seinajoki", "suonenjoki", "tampere", "tornio", "turku", "tuusula", "forssa", "hamina", "hankasalmi", "hanko", "hauho", "heinola", "helsinki", "hyvinkaa", "hameenlinna", "espoo", "jyvaskyla", "jamsa", "jarvenpaa")
• start_date string nullable — Lower bound of the listing date window (YYYY-MM-DD) (examples: "2026-07-01")
• end_date string nullable — Upper bound of the listing date window (YYYY-MM-DD) (examples: "2026-12-31")
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "AfishafiEvent")
• id integer required
• description string nullable
• start_at string nullable
• end_at string nullable
• city string nullable
• organizer string nullable
• price number nullable
• currency string nullable
• ticket_url string nullable
• images array (default: [])
• view_count integer 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.