Letterboxd film
A film on Letterboxd: title, original title, year, tagline, synopsis, runtime, average rating with rating and review counts, poster, backdrop, directors, cast with characters, crew by role, studios, countries, primary and spoken languages, alternative titles, genres and themes, every release (type, date, country, certification, note), IMDb and TMDB ids, and the page's popular reviews (author, rating, likes, comments, spoiler flag, excerpt, link). With include=stats it also returns watch_count (members who watched it), list_count (lists it appears in), likes, top500_rank (its place in the Letterboxd Top 500, else null), and, when available, fans and rating_histogram (count and percent per half-star rating; null when not available).
Every response includes credits_used: the credits this call cost.
Parameters
| name | type | description |
|---|---|---|
slug | string | The film's slug from letterboxd.com/film/<slug>/, e.g. parasite-2019. Example: parasite-2019 |
url | string | Or a letterboxd.com/film/... link. |
include | stats | stats adds member statistics (watches, lists, likes, Top 500 rank) and the ratings histogram with fans when available (slower). |
Every endpoint also takes fresh, raw, fields (see lean responses and caching).
Example
curl "https://api.api.sh/letterboxd/v1/film?slug=parasite-2019" \
-H "x-api-key: $APISH_KEY" import os, requests
res = requests.get(
"https://api.api.sh/letterboxd/v1/film",
params={"slug": "parasite-2019"},
headers={"x-api-key": os.environ["APISH_KEY"]},
timeout=120,
)
res.raise_for_status()
data = res.json() const url = new URL("https://api.api.sh/letterboxd/v1/film");
url.searchParams.set("slug", "parasite-2019");
const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); Response
A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).