OAuth in REST API 1.1


#1

hi,

I was earlier using search API for searching but as now it has been depreciated so i’m trying to implement OAuth in new url but getting error .

Request :https://api.twitter.com/1.1/search/tweets.json?q=uk.msn.com since:2012-12-11 until:2012-12-12 source:web&since_id=&max_id=&result_type=recent&count=100
Base String formed–GET&https://api.twitter.com/1.1/search/tweets.json&count=100&max_id=&oauth_consumer_key=xxxx&oauth_nonce=89dd4dfbcb9ea87855847b5921c2c58b&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1354019703&oauth_token=192886379-MTUaeFWsEgj3spK0biXV3KzGMRlR7DwUfa5yOXet&oauth_version=1.0&q=uk.msn.com since:2012-12-11 until:2012-12-12&result_type=recent&since_id=

It would be appreciated if you can please look into this and suggest me any changes are required.

Thanks in advance…


#2

If you’re using a colon character (or any reserved characters, such as spaces) in API v1.1, you’re going to want to URL/percent encode it. API v1.1 is stricter on following HTTP and OAuth requirements.