Letterboxd hub

Letterboxd Tags API

A member's tags with their film counts, most used first, ready to join to films and reviews.

GET /v1/letterboxd/users/{username}/tags

1 credit Failed requests are free A not-found answer is still charged

About this endpoint

GET /v1/letterboxd/users/{username}/tags returns data.user, and data.tags. Each tag has name, slug and count. The name keeps the member's own spelling and spaces, while the slug is the URL form, so criterion channel and criterion-channel appear together as name and slug. count is the number of films under the tag and is nullable when not available.

One call returns up to 120 tags; there is no page or cursor parameter and no next page. Tags are ordered by use. Join the name or slug to reviews and lists that carry tags.

Letterboxd Tags API FAQ

What is the difference between name and slug?

name is the tag as the member wrote it, including spaces and capitalisation. slug is the lowercase path form used in URLs. Both are returned so you can display one and link or join with the other.

How many tags does one call return?

Up to 120, the most used first. The route takes no page or cursor, so a member with more tags than that gets the first 120 only.

Why can count be null?

The count is nullable because it is not always available. A null means unknown, while a number is the films under that tag at the time of the response.

How many credits does a tags lookup cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.

What does lookupStatus mean here?

found means the member exists, even with no tags. not_found means the username does not exist, and data.user is null.