🐛 getAnimeEpisodes and getAnimeEpisodeById endpoints return different dates in aired field
#567
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
It seems like getAnimeEpisodes endpoint returns a date in UTC+0 without shifting actual date and time.
2025-04-25T00:00:00+00:00and2025-04-25T00:00:00+09:00are different timestamps.See for
airedfield in examples below.https://api.jikan.moe/v4/anime/59833/episodes?page=1
{ "pagination": { "last_visible_page": 1, "has_next_page": false }, "data": [ { "mal_id": 1, "url": null, "title": "Red Stream Explosion!", "title_japanese": "レッドストリーム・エクスプロージョン！", "title_romanji": null, "aired": "2025-02-25T00:00:00+00:00", "score": 4.61, "filler": false, "recap": false, "forum_url": "https://myanimelist.net/forum/?topicid=2211935" }, { "mal_id": 2, "url": null, "title": "Beware of Impostors!", "title_japanese": "偽者注意！", "title_romanji": "Nisemono chuui! ", "aired": "2025-04-25T00:00:00+00:00", "score": 4.76, "filler": false, "recap": false, "forum_url": "https://myanimelist.net/forum/?topicid=2211933" } ] }https://api.jikan.moe/v4/anime/59833/episodes/2
{ "data": { "mal_id": 2, "url": "https://myanimelist.net/anime/59833/Kono_Subarashii_Sekai_ni_Shukufuku_wo_3__Bonus_Stage/episode/2", "title": "Beware of Impostors!", "title_japanese": "偽者注意！", "title_romanji": "Nisemono chuui!", "duration": 0, "aired": "2025-04-25T00:00:00+09:00", "filler": false, "recap": false, "synopsis": "One winter day. While Kazuma was stuffing his face with skewers at a food stall in the town of Axel, an adventurer called out to him. The man said he was looking for an adventurer named \"Sato Kazuma.\" On the condition that Kazuma would buy him dinner, Kazuma told him the legend of \"Sato Kazuma,\" and the man and the three female adventurers in his party were so moved that they shed tears...!?" } }Expected Behavior
Dates should be equal in both endpoints.
Steps To Reproduce
No response
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: