/letterboxd/lists

POST /api/letterboxd/lists

Price: 10 credits

Get a Letterboxd list by URL (or owner username + list slug): title, owner, description, like and comment counts, and the ranked films it contains.

How to use it

Fetch a Letterboxd list by full URL, or by list slug together with the owner username. Returns one item with alias, owner, name, description, like_count, comment_count, film_count and films (ranked, each with id/alias/name/year/image). Set count to control how many films to return.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• list string required — Letterboxd list slug (with 'user' set) or a full list URL (examples: "2026", "https://letterboxd.com/davidehrlich/list/2026/"; minLength: 1)
• user string nullable — List owner username (required when 'list' is a bare slug) (examples: "davidehrlich")
• count integer required — Max number of films to return (min: 1)

Response

• @type string (default: "LetterboxdList")
• alias string required
• url string required
• name string nullable
• owner string nullable
• owner_url string nullable
• description string nullable
• like_count integer nullable
• comment_count integer nullable
• film_count integer nullable
• films array (default: [])
  • @type string (default: "LetterboxdFilmSummary")
  • id integer nullable
  • alias string required
  • url string required
  • name string nullable
  • year integer nullable
  • image string nullable
  • owner_rating number nullable
  • is_liked boolean (default: false)
  • is_rewatch boolean (default: false)

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 — List not found 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.