Changelog
Added deleted entries lists for deleted IDs
GET /v1/anime/deleted(Browse deleted anime entries)GET /v1/manga/deleted(Browse deleted manga entries)
Interest Stacks have been added to Tenrai v1, bringing public MyAnimeList Interest Stack browsing to the API.
New Main Interest Stacks Category:
GET /v1/stacks(Browse/search all public interest stacks)GET /v1/stacks/:id(Get full interest stack details, including entries in source order)
New Entity-Linked Interest Stack Endpoints:
GET /v1/anime/:id/stacks(Get all public interest stacks for an anime)GET /v1/manga/:id/stacks(Get all public interest stacks for a manga)
Public rate limits have increased to 120 requests per minute and 4 requests per second.
Featured Articles have been added. While originally planned for Jikan v5, we've brought them forward to Tenrai v1.
New Main Articles Category:
GET /v1/articles(Browse/search all featured articles)GET /v1/articles/tags(Get all article tags & counts)GET /v1/articles/:id(Get full article details)
New Entity-Linked Article Endpoints:
GET /v1/anime/:id/articlesGET /v1/manga/:id/articlesGET /v1/people/:id/articlesGET /v1/characters/:id/articles
GET /v1/anime/:id/forum)The Anime Forum endpoint is now live. Manga /forum will come soon.
- Episode Threads Only: Currently returns episode discussion threads.
- Jikan v4 Compatible: Uses the exact same schema as Jikan v4 (supports
filter=episode).
GET /v1/anime/:id/episodes)Anime episodes now expose individual cover images where available.
- Source: Cover images are sourced from Crunchyroll (since that's what MAL uses and links on their pages).
- Note: If an anime isn't available on Crunchyroll, cover images may be missing for now. We are working on expanding image coverage for titles beyond Crunchyroll catalogue in future, along with higher quality covers.
We've removed the 3 character minimum limit from all search endpoints.
Server keys now have their own separate cache. All responses are cached for 10 mins. Meaning server key users will be able to access updated information slightly quicker than public api users.
We've also optimized and accelerated the top and seasons endpoints. These endpoints are frequently used in home pages of many applications, so improvements are very meaningful here. Your apps should hopefully be a little snappier now.
SFW filtering is now available for:
- Search and browse endpoints:
GET /v1/animeGET /v1/anime/idsGET /v1/mangaGET /v1/manga/idsGET /v1/seasons/{year}/{season}GET /v1/seasons/nowGET /v1/seasons/upcomingGET /v1/schedules
- Top and random endpoints:
GET /v1/top/animeGET /v1/top/mangaGET /v1/top/reviewsGET /v1/random/animeGET /v1/random/manga
- Anime and manga related-content endpoints:
GET /v1/anime/{id}/fullGET /v1/anime/{id}/relationsGET /v1/anime/{id}/recommendationsGET /v1/anime/{id}/newsGET /v1/manga/{id}/fullGET /v1/manga/{id}/relationsGET /v1/manga/{id}/recommendationsGET /v1/manga/{id}/news
- Character endpoints:
GET /v1/characters/{id}/animeGET /v1/characters/{id}/mangaGET /v1/characters/{id}/full
- People endpoints:
GET /v1/people/{id}/animeGET /v1/people/{id}/mangaGET /v1/people/{id}/voicesGET /v1/people/{id}/full
- Recommendation and review feeds:
GET /v1/recommendations/animeGET /v1/recommendations/mangaGET /v1/reviews/animeGET /v1/reviews/manga
- Normal SFW filtering excludes:
- Anime rated R+ or Rx
- Hentai-tagged content
- Erotica-tagged content
- Added a new
sfw-strictflag wherever SFW filtering is available. Strict mode adds Ecchi filtering on top of the normal SFW exclusions. - Strict filtering only takes effect when SFW filtering is enabled.
- Full/detail endpoints continue returning the requested root anime, manga, character, or person. SFW filtering applies to referenced media returned inside relations, recommendations, appearances, voice roles, and news relationships etc...
These changes should allow for much better fine control over the contents you want displayed within your apps.
We've also updated Ratings filters in all endpoints that have them to support use of multiple ratings within a single request, same as we currently allow with types.
/v1/news: GET /v1/news for paginated news lists with search and tag filtering, GET /v1/news/:id for full news details with related anime/manga details, and GET /v1/news/tags to list news categories with counts.title, views, likes, dislikes, comment_count, published_at, duration, privacy_status, region_restriction, and embeddable) for trailers and promotional/music videos in the /anime/:id, /anime/:id/full, and /anime/:id/videos endpoints.images object containing JPG and WebP paths) to related entries in the /anime/:id/relations and /anime/:id/full endpoints.media_type of related entries (e.g. Light Novel, Manga, Novel, TV, etc.) to the /anime/:id/full, /anime/:id/relations, /manga/:id/full, and /manga/:id/relations endpoint responses.replies count (number of forum replies) to the /anime/:id/episodes and /anime/:id/episodes/:episode_id endpoint responses./random/anime, /random/manga, /random/characters, and /random/people returning the same result on every request. Responses are no longer cached.moreinfo field containing trivia and detailed notes to the /anime/:id/full endpoint response.synopsis) to the /anime/:id/episodes endpoint response.type, status, sfw, rating), optional field inclusion (include=title,type), result totals, and updated_at filtering by ISO 8601 date-time or Unix timestamp in the /anime/ids and /manga/ids endpoints. Corrected manga IDs example schema metadata.favorites count to the person schema inside the /anime/:id/characters endpoint response./s/ paths) were missing the cdn. prefix. They now correctly resolve to https://cdn.myanimelist.net.https://cdn.myanimelist.net/images.