supermarcus / myanimelist-api-specification

An unofficial API specification for MyAnimeList

Hi there 😀 you're viewing Marcus's Github profile.

• ✨ I am an open-source advocate (list of projects).
• 🏫 Currently pursuing Computer Science degrees.
• 💬 Talk to me about mobile software development, embedded systems, and computer networks.

myanimelist-api-specification's Issues

New Authorisation

MyAnimeLIst now uses OAuth2 for authorisation. The docs here should be updated to match this with examples. The MAL docs are not that great.

{"message":"","error":"forbidden"} all the time

https://api.myanimelist.net/v2/anime

NSFW field only has two possible values

Currently(17.08.2021) all animes on MAL have nsfw tag as either white or gray

Feature request: OpenAPI / Swagger specification

It would be interesting to have a OpenAPI or Swagger specification with this information.

Updating the number of watched episodes

I found an issue regarding this section: https://github.com/SuperMarcus/myanimelist-api-specification#update-entries. It says:

The request parameters can be one of the entries in the MyListStatusObject

This is, however, not exactly true. When sending num_episodes_watched field, the server returns an error:

{"message":"This form should not contain extra fields.","error":"bad_request"}

The field should be in fact called num_episodes_watched when making a PUT/PATCH request. The response will still contain num_watched_episodes. Like so:

RequestBuilder {
    method: PATCH,
    url: "https://api.myanimelist.net/v2/anime/918/my_list_status",
    headers: {
        "authorization": "Bearer ...",
        "content-type": "application/x-www-form-urlencoded",
    },
}
num_watched_episodes=1

Response: {"status":"on_hold","score":0,"num_episodes_watched":1,"is_rewatching":false,"updated_at":"2020-04-17T20:47:36+00:00","priority":0,"num_times_rewatched":0,"rewatch_value":0,"tags":[],"comments":""}