/bookmyshow/events/search

POST /api/bookmyshow/events/search

Price: 20 credits

Search BookMyShow events, plays, sports or activities in a city by category, language, genre, tag, date and price band: event code, title, venue, category, starting price, date label, genres, languages, tags and poster

How to use it

Pass a returned id to bookmyshow/events for dates, venues and ticket prices. Filter slugs differ per city and kind; an unknown slug returns no results.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city string required — BookMyShow city alias (examples: "mumbai", "bengaluru", "delhi-ncr")
• kind string — Listing to search (default: "events"; one of: "events", "plays", "sports", "activities")
• categories array nullable — Category slugs (examples: ["comedy-shows"], ["music-shows","workshops"])
• languages array nullable — Language slugs (examples: ["hindi"], ["english"])
• genres array nullable — Genre slugs (examples: ["drama"], ["comedy"])
• tags array nullable — Tag slugs (examples: ["outdoor-events"], ["kids-allowed"])
• date string nullable — When the event takes place (one of: "today", "tomorrow", "this-weekend")
• price string nullable — Ticket price band (one of: "0to0", "0to500", "501to2000", "2001")
• sort string — Result order (default: "relevance"; one of: "relevance", "bestSelling", "priceLowToHigh", "priceHighToLow", "earliestEventFirst", "newestEventFirst")
• count integer required — Max number of results (min: 1; max: 2000)

Response

• @type string (default: "BookMyShowCard")
• id string required
• group_id string nullable
• url string nullable
• product string nullable
• venue string nullable
• category string nullable
• certificate string nullable
• price_from number nullable
• price_label string nullable
• currency string (default: "INR")
• badge string nullable
• rating number nullable
• votes_label string nullable
• likes_label string nullable
• categories array (default: [])
• genres array (default: [])
• languages array (default: [])
• tags array (default: [])
• region_code string nullable
• starts_at integer nullable
• ends_at integer nullable
• venue_address string nullable
• image 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 — BookMyShow has no city under that 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.

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.