/eventsge/events/search

POST /api/eventsge/events/search

Price: 5 credits

Search Events-GE events (Russian-language events across Georgia) by keyword, city, category, venue, hall and date range. Each item is an event with title, annotation, description, session dates with status, category, venue and address, city and country, age restriction, hall, performers, ticket price and currency, cover image and gallery and the event page URL.

How to use it

Search Events-GE events. Optional filters: keyword (full-text), city (Tbilisi/Batumi/Rustavi/Poti), category (slug, e.g. rok/boi), place (venue id), hall (hall id), date_from/date_to (YYYY-MM-DD, by start date), date_type (active = upcoming, past). sort orders by event start date (asc = soonest first). lang selects the content language (ru/en/ka). Set count to how many results you want. Each item has id, event_source_id, title, annotation, description, start_at/end_at, dates, category/category_slug/category_type, venue, address, city/city_slug, country, restriction, hall, performers, price/currency, image, images and source_url.

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 (examples: "концерт", "Меладзе")
• city string nullable — City to filter by (one of: "tbilisi", "batumi", "rustavi", "poti")
• category string nullable — Category slug to filter by (examples: "rok", "boi")
• place integer nullable — Venue (place) id to filter by
• hall integer nullable — Hall id to filter by
• date_from string nullable — Only events starting on or after this date (YYYY-MM-DD) (examples: "2026-08-01")
• date_to string nullable — Only events starting on or before this date (YYYY-MM-DD) (examples: "2026-09-01")
• date_type string — Whether to return upcoming or past events (default: "active"; one of: "active", "past")
• sort string — Sort by event start date (default: "asc"; one of: "asc", "desc")
• lang string — Content language (default: "ru"; one of: "ru", "en", "ka")
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "EventsgeEvent")
• id integer required
• event_source_id integer nullable
• annotation string nullable
• description string nullable
• start_at string nullable
• end_at string nullable
• dates array (default: [])
  • @type string (default: "EventsgeEventDate")
  • id integer nullable
  • started_at string nullable
  • finished_at string nullable
  • status string nullable
• is_periodical boolean nullable
• category string nullable
• category_slug string nullable
• category_type string nullable
• venue string nullable
• address string nullable
• city string nullable
• city_slug string nullable
• country string nullable
• restriction string nullable
• hall string nullable
• performers array (default: [])
• price number nullable
• currency string nullable
• image string nullable
• images array (default: [])
• qna array (default: [])
  • @type string (default: "EventsgeEventQna")
  • question string nullable
  • answer string nullable
• source_url string nullable
• lang string nullable

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.