/bookmyshow/events

POST /api/bookmyshow/events

Price: 10 credits

Get a BookMyShow event, play, sports or activity listing by event code or URL: title, category, genres, languages, tags, description, age range, duration, dates, and every session with venue address and coordinates, start and end time, status and ticket offers with prices

How to use it

Find event codes with bookmyshow/events/search; movies use bookmyshow/movies.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• event string required — BookMyShow event code or event page URL (examples: "ET00513896", "https://in.bookmyshow.com/events/abhanga-repost/ET00513896")

Response

• @type string (default: "BookMyShowEvent")
• id string required
• group_id string nullable
• url string nullable
• category string nullable
• genres array (default: [])
• languages array (default: [])
• tags array (default: [])
• attributes array (default: [])
• mode string nullable
• status string nullable
• is_paid boolean nullable
• description string nullable
• age_range string nullable
• duration_minutes integer nullable
• starts_at integer nullable
• ends_at integer nullable
• venue_code string nullable
• images array (default: [])
• sessions array (default: [])
  • @type string (default: "BookMyShowSession")
  • venue_name string nullable
  • address string nullable
  • locality string nullable
  • region string nullable
  • postal_code string nullable
  • country string nullable
  • latitude number nullable
  • longitude number nullable
  • starts_at integer nullable
  • ends_at integer nullable
  • door_time string nullable
  • status string nullable
  • attendance_mode string nullable
  • price_min number nullable
  • price_max number nullable
  • currency string nullable
  • availability string nullable
  • offers array (default: [])
    • @type string (default: "BookMyShowOffer")
    • name string required
    • price number nullable
    • currency string nullable
    • availability string nullable
    • valid_from integer nullable
    • valid_until integer 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 event 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.

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.