Goodreads Developers discussion
JSON endpoints?
message 1:
by
Isaac
(new)
Jan 19, 2014 03:53PM
Is there any hope of getting API data in JSON anytime soon? XML is unpleasant and heavy to work with, especially in a mobile application.
reply
|
flag
Sorry, that's not in the current plans.
+1 for json endpoints. Hopefully you'll consider it one day.
+1 We would love to use a JSON endpoint as we can process that much faster and easier.
Here's my +1 for JSON endpoints. Definitely preferable over XML.
+1 for JSON endpoints. XML feels too 1998 :)
Sending JSON should be fairly easy. I wonder why it is not prioritized. Apart from how easy it is to use by clients, the payload is also very light and improves latency of all apps (including your own mobile apps!).If you need help. some of us can put in effort to build this for you. For the number of apis exposed. It should be a maximum 2-4 week effort!!
I've noticed that basically all the new feature requests for the API are rejected. I wonder if Goodreads is planning on adding more features to the API, or if they are planning on stopping development for it, or worse, take it offline :(
It’s a pity! There currently is no other API around with as many reviews and ratings. There have been feature requests by a lot of developers since 2011 to include a fully working JSON-api (preferably REST).As in the last 5 years nothing happened I don’t think this API will every be developed any further. You are giving away a possibility here for lots of people to use your API and promote your website by showing a link / logo to your website (as requested in the developer license agreement).
I guess it’s only a matter of time that another service establishes a developer friendly version of Goodreads where the staff actually cares about what people want to do with the API.
It really is a pity :/
GR has zero interest in actually doing anything with JSON endpoints. It really is a pity as it's a very small amount of effort to bring them up to the current standard.
It really is not that hard to implement a proper JSON-REST-API!https://en.wikipedia.org/wiki/Represe...
Goodreads, hire me and I'll implement JSON responses in the REST API myself
Nishad wrote: "Goodreads, hire me and I'll implement JSON responses in the REST API myself"Haha! I can just see the interview. "Nishad, why do you want to work here?" "I just need some json endpoints!"
+1 for json.Please provide response data in json too.
Me and other developers are eagerly waiting for this. :)
+1 for JSON, that would be incredibly helpful!
Michael wrote: "https://www.goodreads.com/jobsThanks for you enthusiasm!"
Thank you for taking our requests to heart! :)
Nishad wrote: "Goodreads, hire me and I'll implement JSON responses in the REST API myself"+1 for hiring Nishad!
Michael wrote: "https://www.goodreads.com/jobsThanks for you enthusiasm!"
Ha, I just read this! Fortunately, I'm qualified for one of the open positions. Just applied, fingers crossed.
Nishad wrote: Ha, I just read this! Fortunately, I'm qualified for one of the open positions. Just applied, fingers crossed.
Good luck :) I was thinking about applying, but I don't think I'm *quite* qualified yet. A few more years in the biz and maybe. :P
Nishad wrote: "Goodreads, hire me and I'll implement JSON responses in the REST API myself"Hi, Nishad, any update about GR JSON endpoints? :))
I agree. XML is much harder to work with. JSON is much better. Better performance all around.Currently I use a Site called LibraryThing.com . The community is smaller, but the API is much better and gives JSON. I would like to migrate my Apps to use GoodReads because the community is larger, and there are better tie-ins to social media, but they are missing a couple of key features including the fact that they have no interest in adding any features at all to their API.
I've been monitoring this forum for a long time (a few years), all I see here is a bunch of "+1, I want this too", and a bunch of no response from the GoodReads staff.
Anyone thought of writing an intermediary for parsing the XML to JSON?
Ohh so there's no way of getting all books. Blast, was hoping I might be able to set up a GraphQL schema :-(
Hi I am new to goodreads and a beginning programer. I am trying to return json for book reviews using an ajax get method.the url I have tried is:
https://www.goodreads.com/api/format=...
what is the correct one?
big thanks!
Hi Paul, unfortunately you won’t find one because it doesn’t exist. You will need to accept XML and transform that at your end.
Why do they say json is available in the documentation?Anyway, I am finding what I need with google books
XML to Json conversion won;t work all the time owing to attribute mapping issues...they need to find a way...
It looks like maybe some endpoints now give json, but not the major ones. I'm getting book ratings/reviews details in json (https://www.goodreads.com/api/index#l...). Maybe they are slowly adding it in.
@Paul Congratulations on completely misunderstanding what the problem is. Perhaps you should take your own advice and learn about the advantages and disadvantages of various formats first? Anyway... +1 for json in the goodreads api
