> **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/myanimelist/user-reviews>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/myanimelist/user-reviews.mdx>

---

# MyAnimeList User Reviews API

Every review a public member has written, with ratings, reactions and full text.

`GET /v1/myanimelist/users/{username}/reviews` returns `data.username`, `data.reviews[]` and `page`. Each review has `title` (the reviewed anime or manga), `reviewer`, `postedAt`, `tags`, `rating`, `helpfulCount`, `text`, `permalink` and the seven `reactions` counts, the same shape used by the anime and manga review routes.

The profile shows 20 reviews per page; pass `page.nextCursor` back as `cursor`. A user with no reviews returns `lookupStatus: found` with an empty array; a name that does not exist returns `not_found`.

## Request

- **Endpoint:** `GET /v1/myanimelist/users/{username}/reviews`
- **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/myanimelist/user-reviews)
- **Platform page:** [/platforms/myanimelist](https://www.socialfetch.dev/platforms/myanimelist)

## FAQ

### Can I filter these reviews by title?

Not on this route. It returns the user's review list. To read reviews for one title, use `/anime/{id}/reviews` or `/manga/{id}/reviews`.

### Why is `reviewer` repeated on every row?

The review shape is shared with the title review routes, so each row names its author even though the profile already tells you who it is.

### How many credits does this request 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.

### Is there a page cursor?

Yes. Follow `page.nextCursor` while `page.hasMore` is true; each page is billed separately.