thank you for your reply the base string is: POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.xml&oauth_consumer_key%3D<cons key>%26oauth_nonce %3D266F69C67017B331830A191EB54AB4C5%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1286032490%26oauth_token%3D<oauth token> %26oauth_version%3D1.0%26status%3DThis%2520status%2520is%2520for %2520rent
then i do: EncodeBase64(EncryptHMACSha1(base, consec)) -> consec contains: urlencode(<consumersecret>)&urlencode(<tokensecret>)) On Oct 2, 4:23 pm, Tom van der Woerdt <i...@tvdw.eu> wrote: > The header looks fine, so I guess it's a signature error. What is your > Base String used to make the signature? > > Tom > > On 10/2/10 4:20 PM, eMailaya wrote: > > > hi > > > i deleted my app. re-created it (again as read-write) and gave myself > > an authorization to use it. now i can receive my statuses and my > > followees statuses as many times as i want, i can even get my profile > > image. all is working fine! > > > now i want to update a new status. made sure my info is correct (fact > > is i can receive any info i want) and POSTed to: > >http://api.twitter.com/1/statuses/update.xml, this: status=This+status > > +is+for+rent > > > with the following headers: > > Authorization: OAuth oauth_consumer_key="<my consumer > > key>",oauth_signature_method="HMAC- > > SHA1",oauth_timestamp="1286028752",oauth_nonce="074D9949F81AE0485176287E05A1FCE7",oauth_version="1.0",oauth_token="<the > > correct oauth token, same as when receiving > > data>",oauth_signature="<oauth signature as when receiving data>" > > > but guess what: i get 401 unauthorized. what am i missing? > > is something missing from the above headers? > > or maybe it's something else? > > thanks! -- 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
