/bookmyshow/cinemas

POST /api/bookmyshow/cinemas

Price: 20 credits

Get a BookMyShow cinema's schedule for a day by cinema code or URL: address, coordinates, facilities, cancellation and m-ticket flags, dates with shows, and every movie playing with language, format, certificate and each show's time, screen, availability and seat-category prices

How to use it

Find cinema codes with bookmyshow/cinemas/search for the same city.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• cinema string required — BookMyShow cinema code or cinema page URL (examples: "IMJW", "https://in.bookmyshow.com/cinemas/mumbai/maison-inox-jio-world-plaza-bkc/buytickets/IMJW/20261004")
• city string nullable — BookMyShow city alias of the cinema (examples: "mumbai", "bengaluru")
• date integer nullable — Show day as a unix timestamp, read as an Indian calendar day; today when omitted (min: 0)

Response

• @type string (default: "BookMyShowCinemaSchedule")
• id string required
• name string nullable
• company string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• date integer nullable
• show_dates array (default: [])
• has_cancellation boolean nullable
• is_m_ticket boolean nullable
• has_e_ticket boolean nullable
• has_food_sales boolean nullable
• allows_coupons boolean nullable
• is_multiplex boolean nullable
• is_new boolean nullable
• legend_codes array (default: [])
• facilities array (default: [])
• terms array (default: [])
• movies array (default: [])
  • @type string (default: "BookMyShowVenueMovie")
  • id string required
  • group_id string nullable
  • language string nullable
  • screen_format string nullable
  • certificate string nullable
  • duration_minutes integer nullable
  • genres array (default: [])
  • trailer_url string nullable
  • is_atmos boolean nullable
  • has_content_warning boolean nullable
  • shows array (default: [])
    • @type string (default: "BookMyShowVenueShow")
    • session_id string required
    • starts_at integer nullable
    • time_label string nullable
    • screen string nullable
    • booking_closes_at integer nullable
    • availability_code integer nullable
    • currency string (default: "INR")
    • price_min number nullable
    • price_max number nullable
    • subtitle string nullable
    • screen_attribute string nullable
    • is_atmos boolean nullable
    • has_couple_seats boolean nullable
    • categories array (default: [])

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 cinema under that code in that city 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.