A data dump method

+1 for Access-Control-Allow-Origin: * on non-authenticated, would be helpful for my userscripts 🙂

Hello, I believe there is currently no method of getting the last updated series. The closest we have is to order by "date_added", could it be possible to add a method to order by "date_updated" or something similar. I know that there is no parameter as "date_updated", that is why, I am asking if anything similar can be done, to just get the last updated series?

Hello, I believe I have found a bug, in "categories/search", we cannot see any more than 2500 results, i.e for per page 100 results, after page 25, we cannot see any results, the same behavior is observed from UI as well: https://www.mangaupdates.com/categories.html?page=26&perpage=100&orderby=category

verify tags by mods

Hey every1, i'm trying to get the latest chapter number for a specific series but i'm having trouble understanding and using the API. I assume that to get a series info i just type 'https://api.mangaupdates.com/v1/series/255' into my browser. But this produces a blank page rather than an error response so i'm very confused.

flaffy123, you need to use new ids (e.g. /series/5rducju) converted from base36 to integers:
https://api.mangaupdates.com/v1/series/12539749386

Any chance to add OAuth Authentication (Authorization Code Flow)?
I have plans to create an app to sync reading lists, but I won't ask for the user password. I think OAuth can fill this gap.

MangaDex has plans to replace the existing regular authentication system with an OAuth way.

AniList already implements an OAuth authentication method.

Possibly. We're focused on redoing the front end right now. We may add personal access tokens as a stop gap at some point.

Could someone help me out?

https://api.mangaupdates.com/v1/lists/0/search

This returns:

{"status":"exception","reason":"Field Validation Error","context":{"invalid-input":"base input was not an object"}}

Other requests work just fine, like getting the metadata and options of the list works just fine.

You have to make sure to use post and make sure to set the content type to JSON.

Thanks for the response, it was indeed json related, the payload was not being send in correct format.

It also seems like page & perpage fields are required(docs do not show it as required), when debugging I removed the payload, when the same error was thrown it made me believe it was something else. 😢

Thanks for the help!

Those shouldn't be required... That's kind of odd if you can't get it to work without them.

Found the reason, you need to atleast send an empty JSON as payload, no payload at all will fail.

Are you still thinking of making UI / UX changes? I'm happy to help with a UX review (that's my day job). You are welcome to message me directly if you are interested 😎

NB: I'm not a developer so I can't help with that - not even front-end code.