zapread.com
zapread.com copied to clipboard
Some JSON Api Feature Requests
While working with the api I noticed some things that could be changed, some would make it easier to work with the api, some are just renamings.
Changes I list here might affect other endpoints too, as they contain changes to internal structures.
At the beginning I'm talking about /Messages/GetAlertsTable and related endpoints.
Search doesn't work
The endpoint(s) always get called with a long json body{"draw":1,"columns":[{"data":null,"name":"Status","searchable":true,"orderable":true,"search":{"value":"","regex":false}},{"data":"Date","name":"Date","sea...
Removing or playing with the parameters changes nothing (except date, which creates an error, MessagesController.cs:293?)
My goal is to search for Status=Unread messages and alerts. The site is doing this via JS (I guess).
Implementing the filters in the *Controller.cs' shouldn't break the app as the client already acts like the search works (long json body).
I'm not sure aout the next ones, maybe you can make own issues for them to seperate this.
Anchor Can that be renamed to commentId? Should be a an uint I guess.
FromID FromID should be an uint, not a string
Link Can that be renamed to postid? Should be a an uint I guess.
__RequestVerificationToken It would be nice If I could get a valid token via a json response, to get one without parsing html (am I missing an endpoint?!). Would also reduce traffic quite a bit.