Goodreads Developers discussion
Weird response from user_status.xml and add_to_shelf.xml
date
newest »
newest »
There was a change on how we validate users using OAuth. I'll send you a private message and we can work thru it.edit: actually, can't message you b/c of your privacy settings. Do you have trouble with other API calls or just those two?
Can you send me a private message (thru the Goodreads inbox at the top right) with the exact URL you're posting to? Also, try to do another post, and note the time you did the posts in the email. Thanks.
I'm also having problems with user_status.xml which redirects me to the signup page. This is new code so I initially thought I was doing something wrong, but I'm having a similar issue with code that used to work which I've reported here:http://www.goodreads.com/topic/show/3...
add_to_shelf.xml still works for me though.
Casper.
Casper wrote: "I'm also having problems with user_status.xml which redirects me to the signup page. This is new code so I initially thought I was doing something wrong, but I'm having a similar issue with code t..."Piling on for this one. I have my oauth access token for a user, and I can modify the shelves for a book using add_to_shelf.xml. However, when I attempt to update status using user_status.xml I get a 401 Unauthorized error.
Adam, I see you're using signpost -- it's a bug in the library:http://code.google.com/p/oauth-signpo...
Thanks Casper! Looks like you hit that same bug and blazed the trail for me. Looks like the solution is to use the custom version of signpost attached to the thread (signpost-core-1.2.1.2.jar linked in the last message in the thread).
I'm trying to do a user_status update to user_status.xml and I'm also getting a 404 with HTML. Goodreads API does not seem to understand properly when it's being sent POST forms.My OAuth works because I can add to shelf. It's the user_status.xml endpoint that's busted.
I can see that user_status.json is used on the website, but I've tried that too and it does the same 404 thing. I'm definitely setting my content type header.
Oh god dammit no I was actually doing a GET. Stupid mistake to make but I'm not familiar with this Rust library I'm using :X.



I am authed and using the OAuth token. Was there some change in how these calls are made?