Goodreads Developers discussion

142 views
Help getting started....

Comments Showing 1-2 of 2 (2 new)    post a comment »
dateUp arrow    newest »

message 1: by Craig (new)

Craig (csgriff) | 1 comments Hello there. I'm just a random dev, not associated with any particular company, who wants to write a few Goodreads apps as kind of a hobby (a father of 2, I wrote a local web app years ago which tracks the library books my kids have read...it's now in the thousands for each kid, and I really could use an automated way of generating a Goodreads list...). I've spent the evening looking into OAuth and understanding how that relates to the required fields to sign up as a Goodreads developer (Application Name, App URL, Callback URL, Support URL). I'm assuming that the app name, app url, and support url are used on the Goodreads form allowing the user to grant access to the consumer app. The callback url then is what is called once the user hits "ok".

I totally understand that in order to actually get a real app working, I need these fields to be real. But for the sake of just being able to see the api and Ruby examples (which seem to require user to be a registered developer), can I just put in bogus values for those fields for now, then change them later once I understand what's going on and set up a website to support the full app?


message 2: by Michael (new)

Michael Economy (michaeleconomy) Sorry for taking a while to respond.

Yes, you can fill them up with bogus values, but if you start using the api a lot we might cut you off. :)


back to top