Jeff’s Comments (group member since May 08, 2013)

Jeff’s comments from the Goodreads Developers group.

No new API keys unfortunately. Just use a scraper but be selective about what you scrape and your scrape rste.

Unfortunately, we can’t share the technical details of our specific implementation. Thanks for your interest in our technologies. Good luck with your project!

See the Goodreads Feedback group, subsection on the mobile apps: https://www.goodreads.com/topic/group...

Is this still a problem? We had an outage that day and that might have been what you were seeing.

The GET parameter is user_id and it's for any user. Your user id is 40950206 for example.

Hi, we don't provide access to Kindle Notes and Highlights but thanks for your interest. We may consider this for future changes to the API.

@Powder,

Are you running this in your browser? When I run the URL in Chrome, I get an error because the server returns the book ID bare, not in any XML document.

However, when I look in the source of error page, I see the book ID.

This might work in your own code if you just look at the response contents directly.

The documentation says " Response contains IDs without any markup. "

Dear AbeBooks Traffic team,

Thanks so much for finding this issue. It looks like there is a bug on the website for those books as well. I've filed a ticket for it (GR-35610) and our team should follow up when it is fixed.

Regards, Jeff

Hi Mads,

That won't work unfortunately, and we don't have a method to list books on a group's shelves. Sorry.

Hi Alejandro,

Are you talking about API request usage by all developers? Or API requests using your developer key?

We don't have any API functions that display graphs or any pages that show API usage.

We do not have any current date set to upgrade to Oauth 2.

We use RedLaser, which is owned by eBay and has a variety of integrations available.

Hi, from what I can tell this looks like a bug. I've filed it to our team and hopefully someone can look into it.

Thanks for the report and sorry for the inconvenience.

Hi, we don't have an API method for showing genres or various combined shelves for all users. You can view shelf for a specific user with reviews.list method and passing in a shelf name.

Hi,

You will want to use the reviews.list method. Set the shelf argument to read.

You should be able to test the URL in your browser. You can start with the sample URL given for that method.

Hi Karen,

Thanks for looking into the details for this. Did they say these were blocks on outgoing connections to ports on other servers?

If so, that would probably explain the problem. Port 80 is regular web traffic. Port 25 is SMTP (sending outgoing mail) and port 21 is FTP (upload/download files)

Goodreads API uses HTTPS requests. UBB appears to call on port 443 on Goodreads for HTTPS, which is pretty standard in general.

If they're blocking connections to outgoing connections to servers on those ports, that means that they're blocking most outgoing HTTPS connections in general. Any API requiring HTTPS would probably not be callable from GoDaddy.

There's not much we can do because our API connections require HTTPS. Maybe they'd be willing to make exceptions for specific user accounts if asked?

No, we don't have an API method for that. Sorry.

Hi Ahmed,

Please contact Godreads support.

https://www.goodreads.com/about/conta...

Hi Ethan, thanks for your bug report. We appreciate your looking into this. Is this causing you any other problems with the API?

Hey Daniel,

I saw you posted a Swift OAuth example. Did you work around this problem or is it still an issue?