Goodreads Developers discussion

The Goodreads oauth documentation is very sparse to say the least (http://www.goodreads.com/api/document...).

I'm assuming typical OAuth workflow of:

/oauth/request_token
/oauth/authorize?oauth_token=foo&oauth_callback=http://my.callback.com
/oauth/access_token?oauth_token=foo

Is this correct?

if so, I am having issues with the authorize URL. I request a token and recieve one fine, but then when I hit the authorize URL, I consistently get directed to a page that says "page unavailable. An unexpected error occured...." (seems like a 500 error page).

This is all from an iOS Objective-C application.

For example, the /oauth/authorize URL I am hitting is this:

http://www.goodreads.com/oauth/author...

And since the user isnt logged in on the device, they are redirected to:

http://www.goodreads.com/user/sign_in...

which is the page that is showing the "page unavailable" error message.

Any ideas?

there is no info in the docs as well about if we need to use signatures and things for the OAuth API as well???

We use oauth 1, I highly recommend using a library, although, from what i understand the iOS oauth libs are imperfect.

Docs are available here:
http://hueniverse.com/oauth/

Thanks for the reply.

I am using a library, not writing by hand.

Can you explain why my call for the authorize url at "www.goodreads.com/oauth/authorize?oau..."

redirects to the user/sign_in page but with error content and not a login dialog?

also, does the goodreads oauth requiring signing?

Craig, I recommend using the OAuthConsumer library on iOS. That's the one we use in our iPhone app.

http://code.google.com/p/oauthconsumer/

See if that changes things for you.

Regarding the "page unavailable" error, I am not quite able to reproduce it, meaning I do get the normal sign_in page if I am not logged in when hitting the URL you provided: http://www.goodreads.com/oauth/author...

@Ettore,

I am using the OAuthConsumer library. Its the most stable, and full-featured iOS OAuth library so I use it on all my applications.

Are you attempting to hit that url I provided from the simulator, a mobile device or directly through a browser? It works fine for me in a browser as well, but not in the simulator or a mobile device.

looks like someone else started a thread yesterday with the same issue I'm having on the auth page, so I'm not the only one.

http://www.goodreads.com/topic/show/5...

We are investigating, thanks for your patience.

@Ettore

No problems. Thanks for the update

We identified the problem (mobile sign_in appears to be broken), and we'll fix it today internally. It should appear live in the next few days.

awesome. thanks so much

Are you using a oauth package mandeep? the URL should be spit out by the library.


Here's a really simple example in ruby:

https://www.goodreads.com/topic/show/...

No I'm not using the oauth libaray.

Do you know if and when goodraeds will adopt oauth2? Will oauth be compatible with mobile phone devices?

I would highly recommend using a library, there are oauth libaries available in all modern languages.

We'd like to support oauth2, but don't currently have a timeline for adding that support.

What is your use case? Where are you running the code?

I think suggesting to use "a library" it's not a smart suggestion. There are a lot of libraries out there but they still require very oftern to provide oauth urls.
I think GoodReads IT should public a list of endpoints and the proper way to invoke them.