POST /api/kupatbravo/events
Price: 5 credits
Get full Kupat Bravo event details by numeric id or alias: title, description, image, organizer, duration, date range, cities, price range and all ticket performances (date/time, city, venue, price, ticket availability, buy link).
Fetch a single Kupat Bravo (Israel) event by numeric id or alias slug. Returns one item with title, description, image, organizer, duration, badge, start_at/end_at, cities, price/price_min/price_max (ILS), ticket_url and performances[] (each with date/time, city, venue, hall_id, seance_id, price, available_count, buy_url).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)event string required — Event numeric id or alias slug (or full event URL) (examples: "AlBanoIsrael2026", "85337"; minLength: 1)@type string (default: "KupatbravoEvent")id string nullablealias string nullablesource_url string requireddescription string nullableimage string nullablebadge string nullablecities array (default: [])country string (default: "Израиль")venue string nullablestart_at string nullableend_at string nullableprice number nullableprice_min number nullableprice_max number nullablecurrency string (default: "ILS")ticket_url string nullableorganizer string nullableorganizer_id string nullableduration string nullableperformances array (default: [])@type string (default: "KupatbravoPerformance")seance_id string nullablestart_at string nullableweekday string nullablecity string nullablevenue string nullablehall_id string nullableaddress string nullablelatitude number nullablelongitude number nullableprice number nullableprice_min number nullableprice_max number nullablecurrency string nullableavailable_count integer nullablebuy_url string nullablelang string (default: "ru")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 — Event not found (well-formed but nonexistent id or alias) 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.