/bookmyshow/movies/showtimes

POST /api/bookmyshow/movies/showtimes

Price: 20 credits

Get the showtimes of a BookMyShow movie in a city on a day, one record per cinema: cinema code, name and link, cancellation, every show with start time, booking cutoff, language and format, seat availability and the price of each seat category

How to use it

Find movie codes with bookmyshow/movies/search for the same city. A movie with no shows in that city on that day answers 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• movie string required — BookMyShow movie event code or movie page URL (examples: "ET00477911", "https://in.bookmyshow.com/movies/mumbai/drishyam-the-conclusion/ET00477911")
• city string required — BookMyShow city alias (examples: "mumbai", "bengaluru")
• date integer nullable — Show day as a unix timestamp, read as an Indian calendar day; today when omitted (min: 0)
• language string nullable — Show language of a multi-language movie (examples: "hindi", "telugu")
• count integer required — Max number of cinemas (min: 1)

Response

• @type string (default: "BookMyShowCinemaShows")
• movie_id string required
• venue_code string required
• venue_name string nullable
• venue_url string nullable
• date integer nullable
• region_code string required
• has_cancellation boolean nullable
• notes array (default: [])
• is_m_ticket boolean nullable
• has_food_sales boolean nullable
• popularity_rank integer nullable
• shows array (default: [])
  • @type string (default: "BookMyShowShow")
  • session_id string required
  • event_code string nullable
  • starts_at integer nullable
  • time_label string nullable
  • booking_closes_at integer nullable
  • language_format string nullable
  • availability string nullable
  • availability_code integer nullable
  • time_of_day string nullable
  • screen_attribute string nullable
  • badge string nullable
  • has_couple_seats boolean nullable
  • currency string (default: "INR")
  • prices array (default: [])
    • @type string (default: "BookMyShowSeatPrice")
    • category string required
    • price number nullable
    • availability 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 — No shows of that movie in that city on that day, or 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.