POST /api/bookmyshow/movies
Price: 5 credits
Get a BookMyShow movie by event code or URL: title, synopsis, certificate, genres, languages, screen formats, duration, release date, user rating with vote and review counts, review hashtags, cast and crew with person ids, poster, banner and trailer
Find movie codes with bookmyshow/movies/search. Cast and crew person_id values are the ids bookmyshow/persons takes; not every credited person has a profile page, and has_profile false marks the ones that may not, which then answer 412. Reviews are bookmyshow/movies/reviews.
access-token string requiredtimeout 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")@type string (default: "BookMyShowMovie")id string requiredgroup_id string nullableurl string nullabledescription string nullablecertificate string nullablegenres array (default: [])languages array (default: [])formats array (default: [])duration_minutes integer nullablereleased_at integer nullablestatus_label string nullableis_bookable boolean nullablerating number nullablerating_count integer nullableuser_review_count integer nullablecritic_review_count integer nullablehashtags array (default: [])@type string (default: "BookMyShowHashtag")name string requiredcount integer nullableimage string nullablebanner string nullabletrailer_url string nullablecast array (default: [])@type string (default: "BookMyShowCredit")name string requiredrole string nullableperson_id string nullableurl string nullablehas_profile boolean nullableimage string nullablecrew array (default: [])@type string (default: "BookMyShowCredit")name string requiredrole string nullableperson_id string nullableurl string nullablehas_profile boolean nullableimage string nullable422 — 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 movie under that code 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.