Goodreads Developers discussion

Is there any chance to remove 1 request per second limit for application? Today I started developing small tool for Goodreads to manage book series (overall progress, check book series read completion, new books in series i've read and so on). But this kind of task requires many request to goodreads api.

For example - if I have 200 books read, these books come from 10 different books series and every series have 5 more books I need:
- minimum three request to read shelves contents
- 200 request for books
- 10 requests for series
- 50 request for books from series which are not on my shelves

So I have 263 requests to made, which gives me almost 5 minutes at the best (when requests are very quick)!

My application is in very early stage of development, but already is available at the http://aplauso.pl/index.php (mostly because I don't know how to do oauth requests on localhost :) ). Site address is not final (it's my temporary server)

Is there a way to communicate with Goodreads developers and ask them if they still haven't add more request per second ?

I thought that group called 'goodreads' developers would be good place :)

And still we don't get an answer ... xD

hey guys, sorry for the delay: we routinely check the forum but we might be a little slow to reply sometimes, depending how busy we are. But eventually we do reply.

At the current time the rate limit in place is still the official limit.

Some background. The objective of the rather strict limit is to prevent spammy use of the api. This has happened in the past. Despite the Amazon acquisition, we are still a small company and we just can't afford for the public api to become an availability issue. It’s a service we provide that let you access some pretty interesting data: a number of developers have found it valuable and built great apps (e.g. Social Reads for Windows Phones). I’m sure if you reach out to those developers they are willing to share their experiences.

That being said, we have been thinking to change the limit a bit. (Emphasis on a bit.) More to come soon, I hope.

There are still a number of things you can do. For example, structure the app in a way that data is presented differently. Or display some data first, and continue to load data in the background. Implement a caching layer to prevent requesting the same data twice in a row. And so on.