Hi everyone!

I just wanted to know if there was an API for Dynasty Reader yet. I did read some posts about that matter here: http://dynasty-scans.com/forum/topics/526-online-reader-suggestions-for-improvement?page=21 but it seems there's nothing more.
Besides, I found out that chapters have a .json page (e.g. http://dynasty-scans.com/chapters/lovesick_girl.json).
But actually, what I wished for was .json pages for directories, and not for chapters. I would love to have a http://dynasty-scans.com/pairings/maki_x_nico.json page for instance. ^^

Thanks, you rock!

I'm pretty sure Dynasty is a Rails app, so it would likely not be particularly difficult to set up other json responses (render :json, eh?)

It's actually pretty interesting that the chapters have a json response...

It is wait&see then?

Indeed, but I can't see what it would be useful for actually.

If there is interest I can add a few more endpoints for it. What would you be using it for?

The purpose is to give the user an easy access to all the contents tagged as he likes.

Basically, If I want to see all the "Aaaaaargh" tagged contents, I'll just have to put this tag on the application's filters.

last edited at Sep 3, 2015 7:57PM

While I dropped off the radar for years, I do still plan to make that fresh Android app with offline caching (yay for having 2+ years of practical Android experience now), so unless an app isn't desirable for some reason - having more APIs for tags/authors/search, etc, would always be tremendously helpful, as parsing HTML would be kind of doing it wrong on many levels.

If you'd rather have the users browse and search on the actual site, then at least an endpoint for the chapter list of a given title would be great to have - there could be an intent to send the user into the app so they won't have to open and download every chapter individually.

last edited at Sep 12, 2015 5:27PM

Is there any intuitive way to get info about a thread? (Ie: When the last post was.) A feature I'm planning for my userscript for the site will allow people to bookmark threads but there's no way I can think of to get info on the thread without having to load it in the background and grab the last post time manually (which would quickly get to be a crap load of data to be loading on each page, though I'm already considering making it check for updates only every 5 minutes or so anyways) or just checking through the first 2-3 pages of the forums and seeing if any of the bookmarked threads fall on those pages and if so getting the info.

Edit: Also is there anything that would allow me to get the user's id so they don't have to enter it into the script themselves?

last edited at Dec 12, 2015 9:48AM

I have added a few additional JSON end points.

http://dynasty-scans.com/chapters.json / http://dynasty-scans.com/chapters/added.json for recently released/added chapters.

http://dynasty-scans.com/pairings.json for all the directory indexes.

http://dynasty-scans.com/scanlators/dynasty_scans.json for all the specific directory pages.

How would I go about seeing past the first page on pairing pages,
E.G. Trying to pass parameters like this just gives the first page again https://dynasty-scans.com/pairings/maki_x_nico.json?page=2

Don't forget https://dynasty-scans.com/tags.json for all directory tags

I think there should be a tad more consistency in the API.
/tags.json endpoint contains tag objects that don't have any type assigned to them, but an endpoint like/chapters/lovesick_girl.json does.

Not like it's anything major, but still, can make mapping the results to objects a smidge more annoying.

If there is interest I can add a few more endpoints for it. What would you be using it for?

I am currently working on a cross-platform (android, windows, linux, iOS etc.) client for dynasty in my free time, so I'd really love to see a json version for all pages. I'm currently parsing the html of each page to get its content, which works fine, but might cause problems if changes to the pages layout are done. And it blotes the code, of cause.

I think stuff like the directories, the image section and manga series could really use some json endpoints, for example.

So yeah, there is some interest and I would greatly appreciate to see some more endpoints, but I'm also fine without them :)