Says here: http://dev.twitter.com/doc/post/statuses/retweet/:id It's on the internets, so it's true :)
I was toying around with oauth_... header parameters. I get the same message when leaving the callback out. I thought maybe that was the problem (not having a callback at first) Base string: POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fretweet %2F2404341.xml&oauth_callback%3Dhttp%253A%252F%252Fwww.rtl.nl %252Fexperience%252Frtlnl%252F%26oauth_consumer_key %3DI1yQDPyI7WUn2fN9JfFWww%26oauth_nonce %3DYmzNuZ4t6L1uYhzxFzvLjKWTyFoEVE9pyAz569zsX4g%253D %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1283524907%26oauth_version%3D1.0 Again, you can leave out the callback part. On Sep 3, 4:46 pm, Tom van der Woerdt <[email protected]> wrote: > I'm pretty sure that /1/statuses/retweet requires authorization ;-) > > There's one thing I see: > * You are sending a oauth_callback where it's not needed. > > There's something I like to see: > * Your Base String to verify that you are sending the right stuff. > > Tom > > On 9/3/10 4:39 PM, Papa.Coen wrote: > > > ....Whilst the docs state no authorization is required. > > > I think I'm doing something wrong with the OAuth fields I send. But I > > have yet to find out exactly what and how to fix it. I've tried the > > 'text/xml; charset=utf-8' content-type, but this results in the same > > message. > > > Sniffed: > > > POST /1/statuses/retweet/22684354355.xml HTTP/1.1 > > Content-Type: application/x-www-form-urlencoded > > User-Agent: RTL Netherlands OAuth Consumer > > Authorization: OAuth oauth_callback="http%3A%2F%2Fwww.rtl.nl > > %2Fexperience%2Frtlnl%2F", > > oauth_consumer_key="I1yQDPyI7WUn2fN9JfFWww", > > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1283523528", > > oauth_nonce="uupiA1mAr22CmX3D3Lou73hDV7yIYP9G9YjsyuhGN%2FQ%3D", > > oauth_version="1.0", oauth_signature="9HWVDDiftaW%2BZaOxNB692zBop1k > > %3D" > > Host: api.twitter.com > > > HTTP/1.1 401 Unauthorized > > Date: Fri, 03 Sep 2010 14:18:49 GMT > > Server: hi > > Status: 401 Unauthorized > > WWW-Authenticate: Basic realm="Twitter API" > > X-Runtime: 0.00591 > > Content-Type: application/xml; charset=utf-8 > > Content-Length: 163 > > Cache-Control: no-cache, max-age=1800 > > Set-Cookie: k=217.118.160.30.1283523529311927; path=/; expires=Fri, 10- > > Sep-10 14:18:49 GMT; domain=.twitter.com > > Set-Cookie: guest_id=128352352931668878; path=/; expires=Sun, 03 Oct > > 2010 14:18:49 GMT > > Set-Cookie: > > _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCGjK9tcqAToHaWQiJTFiYTNiMDlmMzZmNzdi > > %250AODJjMWRiMmY2OTMyODQ4ZTU0IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy > > %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--53471a68a90cd817bfe9063a156fd56d031dbd4f; > > domain=.twitter.com; path=/ > > Expires: Fri, 03 Sep 2010 14:48:49 GMT > > Vary: Accept-Encoding > > Connection: close > > <?xml version="1.0" encoding="UTF-8"?> > > <hash> > > <request>/1/statuses/retweet/22684354355.xml</request> > > <error>Could not authenticate with OAuth.</error> > > </hash> -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
