/russianemirates/events/search

POST /api/russianemirates/events/search

Price: 10 credits

Search and list Russian Emirates events in the UAE. Filter the upcoming events by keyword, category, emirate and event date range; set archive to browse the full chronological catalogue of past and upcoming events instead. Each event has title, alias, image, start and end date, emirate, country, view count and source url.

How to use it

List Russian Emirates events in the UAE. Set count to how many you want. Filter the upcoming events by keyword, category, emirate (Dubai, Abu Dhabi, Sharjah, ...) and date range (date_from / date_to as YYYY-MM-DD); set archive=true to browse the full chronological catalogue (filters do not apply there). Each item has alias, title, description, image, start_at, end_at (ISO date), emirate, country, view_count 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 title and text
• category string nullable — Restrict to an event category (one of: "concerts", "music", "festivals", "exhibitions", "fairs", "horse_racing", "shows", "art", "creativity", "sport", "competitions", "seminars", "meetings", "holidays", "food", "trainings", "business", "travel", "cinema", "flashmobs", "cartoons", "politics", "diaspora", "circus", "ballet", "musicals", "contests", "forums", "theatre", "conferences", "performances", "dances", "elections", "receptions", "children")
• emirate string nullable — Restrict to a UAE emirate (one of: "dubai", "al_ain", "abu_dhabi", "sharjah", "ajman", "umm_al_quwain", "ras_al_khaimah", "fujairah")
• date_from string nullable — Start of the event date range (YYYY-MM-DD) (examples: "2026-08-01")
• date_to string nullable — End of the event date range (YYYY-MM-DD) (examples: "2026-08-31")
• archive boolean — Return the full chronological catalogue of past and upcoming events. When true the keyword, category, emirate and date filters are not applied; when false the filters narrow the upcoming events list (default: false)
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "RussianemiratesEvent")
• alias string nullable
• description string nullable
• image string nullable
• start_at string nullable
• end_at string nullable
• emirate string nullable
• country string nullable
• venue string nullable
• latitude number nullable
• longitude number nullable
• organizer string nullable
• organizer_url string nullable
• price number nullable
• currency string nullable
• ticket_url string nullable
• view_count integer nullable
• categories array (default: [])
• 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.