Ettore Pasquini Ettore's Comments (member since Oct 26, 2010)


Ettore's comments from the Goodreads Developers group.

(showing 61-80 of 217)

Sep 30, 2014 02:55PM

8095 Look at the getting started section:
https://www.goodreads.com/api/documen...

I don't know which language/environment you are using on your end, but pretty much every one has an implementation of the core oauth infrastructure.
Sep 02, 2014 02:49PM

8095 Craig, I looked into this a big and it sounds like there may be a bug here related to key-authorization. I'm going to file a ticket for further investigation.

In the mean time, have you tried using OAuth?
Sep 02, 2014 02:47PM

8095 moving the discussion to this page, since it's duplicated:

https://www.goodreads.com/topic/show/...
Sep 02, 2014 02:28PM

8095 Hey Craig, you mean this api, correct?
https://www.goodreads.com/api#user.fo...

Let me look into it and I will report back.
Sep 01, 2014 01:33AM

8095 Our terms still stand and should be respected. They do not force 3rd party developers to make their apps free, but as point #9 explained, please contact us in that case.
Aug 21, 2014 08:19AM

8095 Hi Cici, this is very unlikely to happen at this point. Sorry!
Aug 19, 2014 11:25AM

8095 Hey Cici, actually it's just a bug in the docs. Wrap the URL between double quotes and it should work, e.g.:

curl "https://www.goodreads.com/search.xml?..."
Aug 19, 2014 11:06AM

8095 I verified the problem. I'm not sure why it's happening, but i'm going to file a ticket to look into this. Sorry for the inconvenience.

Issuing the request with OAuth (instead of unauthenticated key authorization) should work.
Aug 12, 2014 03:57PM

8095 Sobh, by the way, what i meant in my previous message is that the api does return the Goodreads book_id in the response payload. Just parse the returned data as plain text instead of XML. The only data returned is the book id, with no XML markup.
Aug 12, 2014 03:53PM

8095 Cool... yeah, trust me it's easy to get things mixed up, but it's great you figured it out!

Let us know when you finish your app!
Aug 12, 2014 03:50PM

8095 I assume when you replay the request you also change the nonce. That will need to change per each request (along with time signature).
Aug 12, 2014 03:44PM

8095 yeah, unfortunately that seems like the closest thing. Sorry! We might add genres in the future, but i don't know the ETA for that.
Aug 12, 2014 03:40PM

8095 You would need to use the book#show api.
Aug 12, 2014 03:33PM

8095 agree -- my only answer at this point is to wait for the ticket to be fixed. We'll update this topic when that happens.
Sorry for these issues!
Aug 06, 2014 11:47AM

8095 I'm not familiar at all with Node.js so I can't provide much help there.

However, can you inspect the actual Authentication header in the request and see if it's similar to that of the requests that do work?
Jul 11, 2014 04:51PM

8095 actually, upon further investigation it seems like the api works but reports an incorrect MIME type (application/xml, while it should be plain text). In fact, the HTTP status code of the sample URL is 200 in my testing.

I still filed a ticket to fix the response MIME type.
Jul 11, 2014 04:40PM

8095 Hi Sobh, that api looks broken. I'll file a ticket to investigate on/fix it.
Jul 11, 2014 04:28PM

8095 oh I see what you mean (maybe):

The sample URL is in the following format in the api docs:
https://www.goodreads.com/review/list...

You are right that the URL in the api docs is a little different:
https://www.goodreads.com/review/list...

The way you specify the xml format should be equivalent:
https://www.goodreads.com/review/list...

I tested this using KEY authorization though, for a user who is not private and all the above methods work.

The latter seems like is working for you, but I'll file a ticket to fix the other cases (All the above methods should be equivalent and should all work)

About last question: did you set a application name under https://www.goodreads.com/api/keys ?
Jul 11, 2014 04:05PM

8095 did you notice a "memory" problem? i.e. does this happen only if you repeat the same request twice after a couple seconds? What if you submit 2 requests to the same api endpoint but using different params (still using a couple seconds interval between one and the other)?
Jun 03, 2014 11:09AM

8095 Hi Rosen, Amazon doesn't issue ISBNs for Kindle books, only ASINs.

Unfortunately book/review_counts only works with ISBNs at the moment. You can use the book/show or book/title api to get book data (including ratings) on a per book basis.


topics created by Ettore