/bilety/events/search

POST /api/bilety/events/search

Price: 20 credits

Search and list Bilety.co.il events (Russian-language concerts, theatre, circus, comedy, kids, shows and more across Israel). Filter by free-text keyword, categories and subcategories, cities or whole regions, a quick date window or a custom date range, ticket price range, super-price/discount/tour flags, and choose the sort order. Each event has title, description, image, category, price range, start and end date and featured flag.

How to use it

List Bilety.co.il events in Israel. Set count to how many you want. Filter by keyword, categories (concert/theatre/circus/humor/kids/show/meetings/sport/cinema/exhibitions/excursions), subcategories (concert: pop_rock/estrada/hip_hop/jazz_blues/classic/author_song/folk; theatre: plays/musical/opera/ballet_dance/comedy/drama/detective), cities or regions (a_sharon/jerusalem/north/center/south), period (today/tomorrow/week/weekend/next_weekend/month/three_month) or a date_from/date_to range, min_price/max_price, super_price/discount/tour and sort. Each item has id, alias, title, description, image, source, category, subcategory, price_min, price_max, start_date, end_date, comment_count and is_featured. Use bilety/events with the slug or UUID for full details and sessions.

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
• categories array nullable — Restrict to one or more event categories (one of: "concert", "theatre", "circus", "humor", "kids", "show", "meetings", "sport", "cinema", "exhibitions", "excursions")
• subcategories array nullable — Restrict to concert/theatre subcategories (their parent category is selected automatically) (one of: "pop_rock", "estrada", "hip_hop", "jazz_blues", "classic", "author_song", "folk", "plays", "musical", "opera", "ballet_dance", "comedy", "drama", "detective")
• cities array nullable — Restrict to events held in specific cities (one of: "gercliya", "drom_a_sharon_perekrestok_a_yarkon", "kadima", "kfar_yona", "kfar_saba", "netaniya", "or_akiva", "raanana", "ramat_a_sharon", "tel_mond", "hadera", "abu_gosh", "beyt_dzhemal", "ierusalim", "kibbuc_cora", "maale_adumim", "modiin", "afula", "zihron_yakov", "yokneam", "karmiel", "kibbuc_gan_shmuel", "kibbuc_kabri", "kibbuc_mizra", "kibbuc_eyn_a_horesh", "kibbuc_yagur", "kineret", "kiryat_mockin", "kiryat_haim", "maalot", "naariya", "naceret_ilit", "rayonnyy_sovet_hof_a_karmel", "tveriya", "hayfa", "ariel", "aeroport_siti", "bat_yam", "ganey_tikva", "givataim", "iegud", "lod", "petah_tikva", "ramat_gan", "ramle", "rishon_le_cion", "tel_aviv", "tel_aviv_yaffo", "holon", "ashdod", "ashkelon", "beer_sheva", "kibbuc_givat_brener", "kibbuc_dorot", "kiryat_gat", "latrun", "nes_ciona", "ofakim", "rehovot", "eylat", "yavne")
• regions array nullable — Restrict to events held anywhere in whole regions (one of: "a_sharon", "jerusalem", "north", "center", "south")
• period string nullable — Quick relative date window for upcoming events (one of: "today", "tomorrow", "week", "weekend", "next_weekend", "month", "three_month")
• date_from string nullable — Start of a custom date range (YYYY-MM-DD) (pattern: ^\d{4}-\d{2}-\d{2}$)
• date_to string nullable — End of a custom date range (YYYY-MM-DD) (pattern: ^\d{4}-\d{2}-\d{2}$)
• min_price integer nullable — Minimum ticket price filter (ILS) (min: 0)
• max_price integer nullable — Maximum ticket price filter (ILS) (min: 0)
• super_price boolean — Only events with a special low price (default: false)
• discount boolean — Only discounted events (default: false)
• tour boolean — Only touring events (default: false)
• sort string nullable — Result ordering (one of: "price_asc", "price_desc", "name_asc", "name_desc", "date_asc", "date_desc", "category_asc", "category_desc")
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "BiletyEventCard")
• id string nullable
• alias string nullable
• description string nullable
• image string nullable
• source string nullable
• category string nullable
• subcategory string nullable
• price_min number nullable
• price_max number nullable
• start_date string nullable
• end_date string nullable
• comment_count integer nullable
• is_featured boolean nullable
• country string (default: "Израиль")
• 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.