Goodreads Developers discussion
JSON endpoints?
date
newest »
newest »
In Jekyll, XML as data sources isn't supported, so I'm using a plugin: https://github.com/mcred/jekyll-xml-s...Granted I'm not using Oauth, just public data
so in my jekyll _config.yml:
jekyll_xml:
- data: grbooks
source: https://www.goodreads.com/review/list...
cache: false
and then in my liquid template:
{% assign goodreads = site.data.grbooks.GoodreadsResponse %}
{% for rev in goodreads.reviews.review %}
<div class='book'>
<a href='{{ rev.book.link }}'>{{ rev.book.title }} </a>
</div>
{% endfor %}
5 Years later, still looking for that JSON
Once again, the Eagle soars from the Heaven's and perches itself upon weary Prometheus' body."P...Plus One for JSON endpoints?", Prometheus stammers.
He winces again at the bird's inevitable reply.
+1 to JSON (just for keep the meme ball rolling lol)Btw, I'm building a GraphQL gateway for myself, just in case someone tried the same. My (long term) idea is to include multiple Books APIs under the same gql queries (yes, I'm being optimistic) 😃
Paul wrote: "Are people really too lazy to learn how to parse xml these days?"People shouldn't have to. Especially as XML's relatively larger packet size can cost people money over time if they're using cloud-based servers such as AWS Gateway.
George wrote: " ... Especially as XML's relatively larger packet size can cost people money over time if they'r..."The first of 63 previous who writes this. Apparently, this is not important.
I will be glad to change my mind.
This group's description states "Goodreads staff will participate in this group, and try to keep our API as useful as possible" and yet it's amazing how Goodreads doesn't care about its API and its developer users.Our #1 request — json endpoints — has been completely ignored for years and years.
C'mon, Goodreads. Show us some love.
This is my favorite thread on the whole site. :D
+1, my life is definitely too short to parse XML.
Alexis wrote: "This is my favorite thread on the whole site. :D"Mine too.
(but I'd love for it to be abandoned forever because we got the effing json endpoints)
requests.get("https://www.goodreads.com/book/review... ", params={"key":"KEY", "isbns":isbn})I wrote the following code in python to access one of your api methods, including the proper key and all. But for some reason I am unable to access the contents. Could someone please help me?
I made a JSON endpoint if you guys want to try it. I only did the search endpoint, since that's all I use, but I can do more if anyone wants.https://technobitch.com/goodreads.php...
is equivalent to
https://www.goodreads.com/search.xml?...
but will output JSON instead of XML
Hey y'all! I may be late to this discussion, but I've done some initial work on a GraphQL wrapper for the Goodreads API. It's not exactly JSON (what everyone wants); however, GraphQL returns clean and easy-to-understand query results (think the GETs) and easy to implement mutations (POST, PUTs, DELETEs).
I would be happy if people dried it out and gave some feedback as to how I could improve it as a proper backend for whatever apps they plan on building with the Goodreads API.
Link here:
https://github.com/mcshakes/good_wrap
For now, I only have the read only endpoints for
1) api/author_url/
2) author/show/
3) book/show/
They still give some good info I wish I had BUT I plan on adding more. If you have suggestions or feedback, I would happily take it.
Mac wrote: "Hey y'all! I may be late to this discussion, but I've done some initial work on a GraphQL wrapper for the Goodreads API. It's not exactly JSON (what everyone wants); however, GraphQL returns clea..."
nice work!
Mac wrote: "Hey y'all! I may be late to this discussion, but I've done some initial work on a GraphQL wrapper for the Goodreads API. It's not exactly JSON (what everyone wants); however, GraphQL returns clea..."
Awesome work!👏 I'm doing exactly the same for myself! 😀 I could use and support your work instead...thank you for the initiative!
Iván wrote: "Awesome work!👏 I'm doing exactly the same for myself! 😀 I could use and support your work instead...thank you for the initiative!"I would definitely appreciate that! Yeah, I'm happy to take suggestions on how to improve and make it more usable. This is my first time creating a Wiki as well, where I hope to add proper documentation on usage
Adding format=json to some the endpoints give me back this result:{"status":"406","error":"Not Acceptable"}
Looking at the state of the Goodreads API, it's like I'm living in 2006, not 2020. How can the largest book cataloging website's API not support JSON IN 2020?!
I wish GR was open source. We wouldn't still be using xml in 2020 then. Goodreads, if you need help, you just need to ask - I'd even write your entire API for free (and add in a few features like getting the genre).
Yeah, I would even be willing to chip in to write this API for free... JSON is just overall more portable, not sure why we're using XML at this point... it's just becoming deprecated.
It's insane that there's no JSON endpoint yet! clearly, Goodreads doesn't care about developers!
I've been following this thread from 2018, seems there's nobody on Goodreads checking or caring about this
Paul wrote: "I've been following this thread from 2018, seems there's nobody on Goodreads checking or caring about this"This is very true! This thread started in 2014, after all these years even building a REST API feels a bit outdated 😅.
I think that the best thing we could do as devs is just running our own projects to wrap the poorly featured and documented XML API (p.e. with a GraphQL gateway) and using it in our apps or webs 🤔. I'm doing my wrapper and there's a lot of other people out there doing an amazing job with the tools GR provides as well.
Hopefully, Goodreads people will see value on providing services for devs at some point. They'll be able to take advantage of our work when the time comes and we'll eventually have official support 🤞.
+1 for json endpoint in future I've made a program in python that returns search query in json format with book id, book name, Author name along with book image. Ping me if you need help :)
We've been asking for this for a *very* long time. I feel like Goodreads is treated like the red-headed step child. I don't remember the last meaningful feature.
Folks, Goodreads is deprecating ALL OF ITS API ENDPOINTS. Soon. They've sent notices out to developers warning about it. Sadly, it's not a matter of json vs. xml anymore... they're killing it all.
You can read more about the upcoming deprecation in another topic in this forum called "API deprecation".
Anyway..."
He looks like that over enthusiastic kid :P