/kupatbravo/events/search

POST /api/kupatbravo/events/search

Price: 5 credits

Search and list Kupat Bravo (Israel) events: the full afisha, by genre, by region, by price, by date, by producer, by free-text keyword, or special collections (discounts/popular/archive). Returns event cards with title, image, date range, cities, price range and badge.

How to use it

List Kupat Bravo (Israel) events. With no filter it returns the full afisha. genre, region, price_max and date_facet combine together. keyword (free text), producer (organizer id) and category=popular/archive are standalone modes that can not be combined with the other filters; category=discounts does combine. Set count for how many to return. Each item has title, alias, source_url, image, description, badge, start_at/end_at, cities, country, price/price_min/price_max (ILS).

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 name
• genre string nullable — Event genre / section (one of: "classical_concerts", "israel_concerts", "rock_concerts", "jazz_concerts", "performances", "opera", "ballet_dance", "musicals", "sport", "parks_attractions", "cinema", "standup", "exhibitions", "lectures", "kids_performances", "kids_music", "circus", "story_hour")
• region string nullable — Macro-region of Israel (one of: "north", "ha_sharon", "central", "south", "jerusalem_district")
• producer integer nullable — Producer / organizer id to list their events (>: 0)
• price_max integer nullable — Max ticket price in ILS (min: 50; max: 500)
• date_facet string nullable — Named date range: today, tomorrow, weekend, nextweek (one of: "today", "tomorrow", "weekend", "nextweek")
• category string nullable — Special collection: discounts, popular, archive (one of: "discounts", "popular", "archive")
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "KupatbravoEvent")
• id string nullable
• alias string nullable
• source_url string required
• description string nullable
• image string nullable
• badge string nullable
• cities array (default: [])
• country string (default: "Израиль")
• venue string nullable
• start_at string nullable
• end_at string nullable
• price number nullable
• price_min number nullable
• price_max number nullable
• currency string (default: "ILS")
• ticket_url string nullable
• organizer string nullable
• organizer_id string nullable
• duration string nullable
• performances array (default: [])
  • @type string (default: "KupatbravoPerformance")
  • seance_id string nullable
  • start_at string nullable
  • weekday string nullable
  • city string nullable
  • venue string nullable
  • hall_id string nullable
  • address string nullable
  • latitude number nullable
  • longitude number nullable
  • price number nullable
  • price_min number nullable
  • price_max number nullable
  • currency string nullable
  • available_count integer 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.