/yolo/events/search

POST /api/yolo/events/search

Price: 10 credits

List Yolo events in Tbilisi and Batumi (Georgia). Filter by category, city, service language, price range, date (relative preset or explicit range) and order by price. Optionally narrow by a free-text keyword matched against event titles. Each event has title, category, image, date range, venue, from-price and currency, external ticket url and source.

How to use it

List Yolo (Tbilisi/Batumi, Georgia) events. Set count to how many you want. Filter by category (e.g. theater, musical, festivals), city (tbilisi/batumi), language (en/ka/ko/ru/fr), price_min/price_max (GEL), date (today/this-week/this-month) or an explicit date_from/date_to range, and sort (cheaper/expensive). keyword narrows by event title. Each item has id, alias, title, category, image, start_at/end_at (YYYY-MM-DD), venue, price (from-price), currency, ticket_url 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 — Free-text query matched against event titles (minLength: 1)
• category string nullable — Restrict to a single event category (one of: "musical", "gastronomic", "theater", "cafe", "festivals", "tourism", "exhibition", "kids", "education", "nightlife", "sports", "others", "movies", "spiritual", "new-year", "valentines-day", "womens-day", "mothers-day")
• city string nullable — Restrict to a city (one of: "tbilisi", "batumi")
• language string nullable — Restrict to the event service language (one of: "en", "ka", "ko", "ru", "fr")
• price_min number nullable — Minimum ticket price in GEL (min: 0)
• price_max number nullable — Maximum ticket price in GEL (min: 0)
• date string nullable — Restrict to a relative date range (one of: "today", "this-week", "this-month")
• date_from string nullable — Start of an explicit date range (YYYY-MM-DD or DD.MM.YYYY)
• date_to string nullable — End of an explicit date range (YYYY-MM-DD or DD.MM.YYYY)
• sort string nullable — Order results by price (one of: "cheaper", "expensive")
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "YoloEvent")
• id string nullable
• alias string nullable
• category string nullable
• description string nullable
• image string nullable
• images array (default: [])
• price number nullable
• currency string nullable
• service_languages array (default: [])
• start_at string nullable
• end_at string nullable
• city string nullable
• country string nullable (default: "Georgia")
• venue string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• location_url string nullable
• location_alias string nullable
• ticket_url string nullable
• source_url string nullable
• sessions array (default: [])
  • @type string (default: "YoloEventSession")
  • date string nullable
  • weekday string nullable
  • time string nullable
  • price_min number nullable
  • price_max number nullable
  • currency string nullable
  • buy_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.