> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/letterboxd/users-username-following>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/letterboxd/users-username-following.mdx>

---

# Letterboxd Following API

The accounts a member follows, with each row's profile facts and public counts.

`GET /v1/letterboxd/users/{username}/following` returns `data.user`, and `data.users`. Each row uses the same member summary shape as the followers route: `username`, `displayName`, `avatar`, `badge`, `followersCount`, `followingCount`, `filmsWatched`, `listsCount` and `likesCount`. Use it to map a member's taste network or to collect a seed list of active accounts.

One call returns the first 25 accounts; there is no `page` or `cursor` parameter and no next page. Counts are nullable when not available. The direction matters: this route lists who the member follows, while `/followers` lists who follows the member.

## Request

- **Endpoint:** `GET /v1/letterboxd/users/{username}/following`
- **Credits:** 1 credit
Failed requests are free
A not-found answer is still charged
- **Input:** by username
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/letterboxd/users/username/following/get)
- **Platform page:** [/platforms/letterboxd](https://www.socialfetch.dev/platforms/letterboxd)

## FAQ

### What is the difference from the followers route?

This route lists accounts the member follows. The followers route lists accounts that follow the member. Both return the same member summary rows.

### How many accounts does one call return?

25. The route takes no page or cursor. An empty following list is a found result, not not_found.

### Why are some counts null?

Not every counter is always available. A null means the field was absent from the row, not that the member has zero.

### How many credits does a following 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 following. not_found means the username does not exist, and data.user is null.