/bookmyshow/persons

POST /api/bookmyshow/persons

Price: 20 credits

Get a BookMyShow person by id or URL: name, alias, birth date and place, nationality, designations, biography, spouse and children, debut, full filmography with this person's roles, peers, family and trivia

How to use it

Person ids come with the cast and crew of bookmyshow/movies.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• person string required — BookMyShow person id or person page URL (examples: "24051", "IEIN090440", "https://in.bookmyshow.com/person/ajay-devgn/24051")

Response

• @type string (default: "BookMyShowPerson")
• id string required
• name string required
• alias string nullable
• url string nullable
• gender string nullable
• born_at integer nullable
• birth_city string nullable
• birth_state string nullable
• birth_country string nullable
• nationality string nullable
• designations array (default: [])
• bio string nullable
• image string nullable
• spouse_names string nullable
• children_count integer nullable
• film_count integer nullable
• debut object nullable
  • @type string (default: "BookMyShowFilm")
  • id string required
  • group_id string nullable
  • url_title string nullable
  • url string nullable
  • year integer nullable
  • released_at integer nullable
  • is_release_date_tentative boolean nullable
  • language string nullable
  • genres array (default: [])
  • roles array (default: [])
• films array (default: [])
  • @type string (default: "BookMyShowFilm")
  • id string required
  • group_id string nullable
  • url_title string nullable
  • url string nullable
  • year integer nullable
  • released_at integer nullable
  • is_release_date_tentative boolean nullable
  • language string nullable
  • genres array (default: [])
  • roles array (default: [])
• peers array (default: [])
  • @type string (default: "BookMyShowRelative")
  • id string nullable
  • name string required
  • relation string nullable
  • designation string nullable
  • gender string nullable
  • born_at integer nullable
  • married_at integer nullable
  • marriage_ended_at integer nullable
  • url string nullable
• family array (default: [])
  • @type string (default: "BookMyShowRelative")
  • id string nullable
  • name string required
  • relation string nullable
  • designation string nullable
  • gender string nullable
  • born_at integer nullable
  • married_at integer nullable
  • marriage_ended_at integer nullable
  • url string nullable
• trivia array (default: [])
  • @type string (default: "BookMyShowTrivia")
  • kind string nullable
  • text string required
  • movies 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 person under that id 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.