Goodreads Developers discussion
      bugs
      >
    OAuth API now broken
    
  
  
					date newest »
						  
						newest »
				
		 newest »
						  
						newest »
				 Thanks Michael, appreciate it. I have been bouncing the users to Goodreads support and so far none have reported getting a response so the natives are all a bit restless :)
      Thanks Michael, appreciate it. I have been bouncing the users to Goodreads support and so far none have reported getting a response so the natives are all a bit restless :)
     Thanks for the quick turnaround guys, it worked rather more successfully for me this morning.
      Thanks for the quick turnaround guys, it worked rather more successfully for me this morning.I see no-one has responded to my other thread I created about another bug slightly related to this that is here:
http://www.goodreads.com/topic/show/1...
The problem still exists - when you list what applications you have authorised on the webpage it says "no application", but when you revoke access, it actually puts the full name that I would expect on that page...
 Hi there.
      Hi there.I posted this under questions but am hoping I could get a better audience here:
I am having trouble getting the access token after authorizing. I am doing what another person did in another post (http://www.goodreads.com/topic/show/3...
I am failing at client.request(access_token_url, 'POST'), where I get Exception: Invalid response: 401
Here the access_token_url is http://www.goodreads.com/oauth/access...
Could someone please advise on how to get access token? Is it broken? Thanks in advance!





 
Attempting to retrieve the token/secret key from:
http://www.goodreads.com/oauth/access...
now returns with a 404 error.
In addition it is failing to bring up the authenticate page, when I open it in the browser using this:
http://www.goodreads.com/?oauth_token...
Do some servers need a kick in the teeth on the goodreads side? Or has something been changed that hasn't been communicated here that I have seen?