MyAnimeList User Reviews API
Every review a public member has written, with ratings, reactions and full text.
GET /v1/myanimelist/users/{username}/reviews1 credit Failed requests are free A not-found answer is still charged
About this endpoint
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.
MyAnimeList User Reviews API 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.
Other MyAnimeList endpoints
- Anime titleGET /v1/myanimelist/anime/{id}
- Manga titleGET /v1/myanimelist/manga/{id}
- Anime cast and staffGET /v1/myanimelist/anime/{id}/characters
- Manga castGET /v1/myanimelist/manga/{id}/characters
- Anime statisticsGET /v1/myanimelist/anime/{id}/statistics
- Manga statisticsGET /v1/myanimelist/manga/{id}/statistics
- Anime reviewsGET /v1/myanimelist/anime/{id}/reviews
- Manga reviewsGET /v1/myanimelist/manga/{id}/reviews