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

[firelight]

/user/{id}/followed-manga

1. Why don't chapters follows have the manga ID anymore?
2. Why does every chapter have my user ID instead of it being included once outside of the data array?

 

[YuriM]

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 scanlation for the series?

Same question. Would be quite useful. Not all manga with "Pub. status: Completed" have "end" chapters.

 

[Plykiya]

@firelight Those aren't chapters

@YuriM The presence of a chapter that has matching lastVol and lastChap numbers does not mean that the scanlation is complete, so we don't care about it all that much

 

[veopot]

Is it possible to do so
https://api.mangadex.org/v2/manga/ {id }/chapters
So that it shows only in those languages that are in the user settings in Cookies?

I am from the MangaWatcherX application team, and we are still alive

(writing via google translator)

 

[volcelhmptn]

@MiBi250 sorry i didnt see this earlier, do you mean using something like cors-anywhere?

 

[volcelhmptn]

I've been using the cors-anywhere demo server as a proxy and it works to retrieve everything except chapter pages. whenever i try to get a page i get error 400. it says to include an origin or x-requested-by header but i thought the proxy already sets the origin header? really confused why this is the only type of endpoint that doesnt work.

 

[volcelhmptn]

@veopot почему бы не сделать это самому? для меня что то вроде такого работает:
var ruChapters = chapterArray.data.chapters.filter(chapter => chapter.language == "ru");

 

[veopot]

@volcelhmptn

mangawatcherx app (since 2010 the app exists even older than tachiomi)
does not know how we have everything through json

https://github.com/veopot/mwx-json/blob/main/parsers/mangadex.json


(writing via google translator)

 

[volcelhmptn]

@veopot well if the api doesnt provide filtered chapters you can filter them yourself with javascript. they do provide language tags to do this

 

[veopot]

@Volcelhmptn понятно , пойду думать

 

[YuriM]

It would be nice if you'd have API function to search Mangadex entry by Mangaupdates index. And other manga sites' indexes too. E.g.:
https://www.mangaupdates.com/series.html?id=173324 ->
send to your API: mu=173324 ->
get link to: https://mangadex.org/title/56750/virus-tensei-kara-hajimaru-isekai-kansen-monogatari
PS: currently I have 1 script to scrape/parse all your titles, save md/mu indexes and titles to db,
another script - webserver to return md index and title by mu search,
and TamperMonkey script for MangaUpdates, which uses my webserver script, gets md index and title, and using 5 regexps creates MangaDex link on MangaUpdates title page.
That's uncomfortable.