Dev news: Launching API version 2 (also v1 deprecation notice) | Last updated 2021-01-17

[volcelhmptn]

@teasday I see. That makes sense. Since I'm just playing around with it for learning purposes (as you can tell from my low IQ questions) I'll try that proxy server thing. Thanks for taking the time to explain!

 

[RhiobeT]

@Teasday Hey, sorry to bother you, but I have a quick question: I can't find a way to search a manga based on its links field (for example, to find a manga from its AniList's id), am I missing something or is it simply not implemented yet?
Thanks in advance!

 

[Yvyuw]

@Teasday, greetings. I notice that the api is not returning the last chapter recently added for some titles.
Can it be confirmed?

Edit: btw, it works fine on v1 (mangadex.org/api/) the problem is only on v2 (api.mangadex.org)

Thanks.

 

[Grumpyfelo]

@teasday

This means that one way to get around the CORS issue inside the browser would be to route your api calls via a proxy server - although that obviously means the proxy server may have to take care to not hit our rate limits and get autobanned if several people are using it.

so, if i dont use a vpn i cant use any apps like tachi or neko until api is fixed?
last week if i waited like idk 4 - 6 hours i could see an update on tachi but after the servers imploded the other day i havent seen updates on tachi

 

[Thelonewolf]

Is it just me or did the tachi extension stop getting updates at all after the server problems last week. Like, we used to get the updates a day or 2 after its release on the website but it's completely stopped. And I can't download any of the newly updated chapters that do show up(like the ch81 of drifters).

 

[Teasday]

@RhiobeT Not an option currently.

@Yvyuw Caching troubles, I assume.

@Grumpyfelo I don't know how that relates at all to what I just said there. I was talking about CORS there, it has nothing to do with Tachi, using a VPN or the API needing to be fixed in any way. For the information of @Thelonewolf as well, MangaDex has nothing to do with the development of Tachiyomi, so I can't help you with whatever problem you're having there. I personally don't even use it, much less am a Tachiyomi dev.

 

[Teasday]

In short: Do not ask or talk about Tachiyomi here. I have no fucking clue.

 

[DrMuhammad]

@Teasday This should be pinned. will solve most troubles. I'm serious.

 

[Thelonewolf]

@Teasday best to just pin this up lol. Tons of questions on reddit and the tachi staff were saying that it's due to MD's api caching probs and were rerouting us here

Guess it's time to just transfer all my bookmarked mangas over the MD

 

[Teasday]

@DrMuhammad @Thelonewolf If it's just questions about why is the MangaDex extension for Tachiyomi not working properly, the answer is indeed that our api server caching is messed up and will lead to some inconsistencies between Tachiyomi and the website. There's nothing else I can say about it except that we're aware, we're working on it, there's nothing you need to or can do, you'll just have to wait until it's done.

That all has nothing to do with this thread, however. This isn't a support thread for general users, this is developer news. Do not read this thread thinking there's anything here that would help fix your Tachiyomi issues.

 

[Luxcio]

Question : im mobile user and i dont know how to change API on my phone, so did i have to suffer?

 

[ak0ztik]

Just 1 question, what's the old api url?
Is it api.mangadex.org?

 

[popochun]

@ak0ztik that's v2. v1 endpoint is at mangadex.org/api/

 

[BraveDude8]

@ak0ztik @popochun
mangadex.org/API/v2 and API.mangadex.org/v2 are both v2, the latter is the separate API server. v1 and v2 are accessible from both.

 

[ak0ztik]

@popochun
@BraveDude8
thanks for the response

 

[popochun]

@BraveDude8
Ah goit it. Thanks for the correction.

 

[tbf]

Is there any flag for manga that's received an "end" label, say as in https://mangadex.org/title/3056/, marking the end of the scanslation for the series?

 

[MiBi250]

@volcelhmptn if you are creating a browser extension/user script for mangadex you can simply simpy fetch data from the api without problems. If you create a website that displays data or whatever do not try to fetch data directly via the browser of the client, instead make an request to your own webserver wich then sends a get/post to the mangadex api and returns it to the client.

 

[nolbat]

@Teasday I'm getting incorrect chapter results with this version of API v2 - Chapters - https://api.mangadex.org/v2/manga/46401/chapters. It returns the latest chapter of Yankee JK Kuzuhana-chan as 43 and it should be 44. If I use the old version of API v2 - Chapters - https://mangadex.org/api/v2/manga/46401/chapters it returns the correct latest chapter as 44.

The same thing occurs for EX-ARM. https://api.mangadex.org/v2/manga/18789/chapters incorrectly returns 20 as the latest chapter. https://mangadex.org/api/v2/manga/18789/chapters correctly returns 22 as the latest chapter. I only tried those two manga. Should I go back to using https://mangadex.org/api/v2/manga/ instead of https://api.mangadex.org/v2/manga/?

Thanks

 

[Teasday]

@nolbat Cache problems