v2/manga/
Yeah, I kind of hate it, but the rationale is basically the same as simply adding to a view count on a GET request. I could see the point of flipping the default, but adding the read marker "should" be the default result, if you know what I mean. We'll probably revisit this with v5, but this is partly a matter of sacrificing API purity in favor of minimizing the amount of requests necessary.@Mattish posted:
"GET /chapter/{id|hash}"
"mark_read": "(Optional) Mark the chapter as read. Boolean, default true."
Defaulting to making a change/write on `GET` is misleading, but I can understand the intent behind this. I'd say it's worth considering flipping the default.
Yeah, it was just to achieve parity with v1 since this feature actually did exist, and to have at least one write endpoint to base future work on. I'll probably add like a manga-specific marker endpoints in the near future."POST /user/{id}/marker"
There isn't any way to query read markers and isn't returned on any other endpoints. Is this just WIP?
API:Warning: Manga #37071 is not available. Contact staff on discord for more information.
api/v2/manga/37071/chapters
api/v2/manga/37071/chapters
Sometime during Saturday hopefully.
That's the plan, but it's pretty much going to have all the same problems as the current search. Unless I do some heavy rewriting, which I... don't think I will. We'll see.@Isotab posted:
This is a bit of a non trivial request but is there any chance search will come to the api? I know searching is/was locked to logged in members only but that could just give an error response when there is no cookie present.