/imdb/titles/release-info

POST /api/imdb/titles/release-info

Price: 1 credit

Release dates across all countries and alternate titles (AKAs) by region/language for an IMDb title, including festival and premiere attributes.

How to use it

Fetch release information for an IMDb title by tt-ID or URL. Returns one item with release_dates (each with country, country_code, date and attributes) and akas (alternate titles with country, country_code, language and attributes). Set count to cap how many entries per list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• title_id string required — IMDb title ID (e.g. 'tt0111161') or a title URL (examples: "tt0111161", "https://www.imdb.com/title/tt0903747/"; minLength: 1)
• count integer required — Max number of release dates and AKAs to return (per list) (min: 1)

Response

• @type string (default: "ImdbReleaseInfo")
• id string required
• release_dates array (default: [])
  • @type string (default: "ImdbReleaseDate")
  • country string nullable
  • country_code string nullable
  • date string nullable
  • attributes array (default: [])
• akas array (default: [])
  • @type string (default: "ImdbAka")
  • title_text string nullable
  • country string nullable
  • country_code string nullable
  • language string nullable
  • attributes 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 — Title not found (well-formed but nonexistent IMDb title 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.