/showman/events/search

POST /api/showman/events/search

Price: 20 credits

Search and list Showman events (Russian-language concerts, theatre, shows and stand-up in Israel). Filter by free-text keyword, genre or city, and sort the results. Each event has id, title, alias, source_url, description, image(s), category, genres and currency.

How to use it

List Showman events. Set count for how many to return. Filter by keyword (free text), genre (e.g. Концерт, Театр, Юмор) or city (e.g. Иерусалим, Тель-Авив); city cannot be combined with keyword or genre. Sort with sort (date/title/popularity/rating) and order (asc/desc). Each item has id, title, alias, source_url, description, image, images, category, genres and currency. For schedule, prices and venue use showman/events.

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 to search events by title
• genre string nullable — Filter events by genre (one of: "18+", "Club", "Comedy", "Disco", "StandUp", "Акустический", "Балет", "Бизнес", "Вечеринка", "Встреча", "Выставка", "Голливуд", "Детям", "Джаз", "Документальное", "Инструментальная музыка", "Кино", "Классика", "Концерт", "Лекция", "Метал", "мюзикл", "Новогоднее", "Опера", "Оркестр", "Панк", "Психология", "Рок", "Рэп", "Семейный", "Сказка", "Танец", "Творческий вечер", "Театр", "Украина", "Фестиваль", "Шоу", "Юмор")
• city string nullable — Filter events by city (one of: "Cyprus", "Cyprus Limassol 4540 Paramytha", "Emek izrael", "Kfar Baruch", "Limassol 4540 Paramytha", "Tel-Aviv", "Акко", "Ариэль", "Афула", "Ашдод", "Ашкелон", "Бат-Ям", "Беэр-Шева", "Герцлия", "Иерусалим", "Йокнеам", "Кармиэль", "Кейсария", "Киббуц Ган-Шмуэль", "Кирьят-Гат", "Кирьят-Моцкин", "Кирьят-Оно", "Кирьят-Хаим", "Кирьят-Ям", "Кфар Врадим", "Кфар Вродим", "Кфар-Саба", "Лод", "Маалот", "Модиин", "Наария", "Нес-Циона", "Нетания", "Нетивот", "Ноф а-Галиль (Нацерет-Илит)", "Ор-Акива", "Петах-Тиква", "Раанана", "Рамат а-Шарон", "Рамат-Ган", "Рамле", "Реховот", "Ришон ле-Цион", "Тель-Авив", "Хадера", "Хайфа", "Хариш", "Холон", "эйлат", "Эйлат")
• sort string nullable — Sort events by this field (one of: "date", "title", "price", "popularity", "rating", "menu_order")
• order string nullable — Sort direction (one of: "asc", "desc")
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "ShowmanEvent")
• id string nullable
• sku string nullable
• alias string required
• source_url string required
• description string nullable
• image string nullable
• images array (default: [])
• category string nullable
• genres array (default: [])
• start_at string nullable
• end_at string nullable
• city string nullable
• venue string nullable
• address string nullable
• country string nullable
• price_min number nullable
• price_max number nullable
• currency string (default: "ILS")
• ticket_url string nullable
• event_status string nullable
• attendance_mode string nullable
• is_in_stock boolean nullable
• lang string (default: "ru")
• sessions array (default: [])
  • @type string (default: "ShowmanEventSession")
  • id string nullable
  • start_at string nullable
  • weekday string nullable
  • city string nullable
  • venue string nullable
  • address string nullable
  • price_min number nullable
  • price_max number nullable
  • ticket_url 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.