POST request returned {"message":"Could not authenticate you","code":32} after migrated to API v1.1

[TheTreasureTech]

cjsoftlab, The solution in the link that mitsuaki_i posted fixes the issue. Simply url encode your data for the post of the status or any other post data.

[cjsoftlab]

Not for me. mitsuaki_i’s method (http://stackoverflow.com/questions/14672502/bug-or-spec-change-of-twitter-api-1-1) is applied when posting:

!
'
(
)
*

That’s not my case…unfortunately. Thanks anyway.

[DantewithMWL]

FOUND A SOLUTION - using the Abraham TwitterOAuth library. If you are using an older implementation, the following lines should be added after the new TwitterOAuth object is instantiated:

$connection->host = "https://api.twitter.com/1.1/"; $connection->ssl_verifypeer = TRUE; $connection->content_type = 'application/x-www-form-urlencoded';

The first 2 lines are now documented in Abraham library Readme file, but the 3rd one is not. Also make sure that your oauth_version is still 1.0.

[chiranv]

Same issue here!!

[msolution]

-All worked out- just add the lines above.

[Nagynam99]

All of our POST request would failed after migrate to API v1.1 but GET requests still work fine.

Is there anything else that we need to modify?That’s not my case…unfortunately. Thanks anyway.

[Nagynam99]

API in question to generate the example signature, header and HTTP request, then comparing it to the versions my software was generating. It stood out like a sore thumb then,All worked out- just add the lines above.Abraham TwitterOAuth library. If you are using an older implementation, the following lines should be added after the new TwitterOAuth object is instantiated: post data.

[Nagynam99]

EDIT: what helped me eventually is this thread: https://dev.twitter.com/discussions/10935,i have the same issues with search/tweets when migrating to 1.1GET requests still work fine, HTTP request, then comparing it to the versions my software was generating. It stood out like a sore thumb then.version of API.

[ClinicMattersTV]

they just breeze in here to give unhelpful tips, they really need to consider shutting down this api. it’s not just useless, it does not work, so exhaustive.

[ShanghaiTimes]

Working on the same problem here,

The one sticking point is the error 32 now being returned.
{“message”:“Could not authenticate you”,“code”:32}

I am using the stageWebView, Mobile config, (iPhone), building with AS3 and I can log in, authenticate, and the code even returns a successfuly completed to me - BUT - as it does, I get that error, and the tweet post (status) fails.

The following are traces from various parts of the code.

[SWF] PinPointPremium.swf - 9008565 bytes after decompression 1516:Here we are calling Auth 1639PinPoint Xtra puts ShanghaiTimes here: http://tinyurl.com/9qteqfu 1640:Sending Tweet via Tweetr.as 1 {"errors":[{"message":"Could not authenticate you","code":32}]} Event Complete: Username: ShanghaiTimes User Id: 16xxxxxxxxx OAuth Token: 16xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxqQ OAuth Token Secret: oJExxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxgw [UnloadSWF] PinPointPremium.swf Test Movie terminated.

Has anyone found a definitive solution to this?

[episod]

Take a look at [node:204] for some typical tips in debugging OAuth issues. In particular, I’d look at how you’re encoding characters like the " " (space character) and other aspects of the request like the HTTP verb being used (POST)

[genwebes]

I love you

[renanvaz]

If you are using the TwitterAPIExchange, you must call the “setGetfield” method before “buildOauth”.

[venkat_aspire]

I’m using zend oauth client to connect to twitter api. I had the api working properly for version 1 from which I’m migrating to 1.1. I receive both the request token and response token. When I then request for twitter api users/show.json? with version 1.1 I receive {“message”:“Could not authenticate you”,“code”:32}

I followed all discussions regarding the same and nothing worked . the following were the details

url : https://api.twitter.com:443/1.1/users/show.json?screen_name=venkat_aspire

Header details
(
[0] => Host: api.twitter.com
[1] => Connection: close
[2] => Accept-encoding: gzip, deflate
[3] => User-Agent: Zend_Http_Client
[4] => Authorization: OAuth realm="",oauth_consumer_key=“hpxxxxxxxxxxxxxxxxxw”,oauth_nonce=“a7c01abe4c10d0c955b2bbee724ae2d7”,oauth_signature_method=“HMAC-SHA1”,oauth_timestamp=“1386944690”,oauth_version=“1.0”,oauth_token=“97xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxCY”,oauth_signature=“9ARUtWNM2P0L2xoXW%2F5jneXT%2FlI%3D”

Can anyone please help me on this?

[gfdesignes]

Matteo are you Italian ? If yes… can you add me plz ?

[fjbotti]

Hello all! I’m facing the same issue “Could not authenticate you” Code 32. Has anyone find a solution to this problem? I’m using Abraham’s library for twitteroauth and I got the last gitbhub version.

TIA,
Federico

[lanka_]

Thank you Dante!

[felpone]

I’ve the same problem using library codebird.js and app only authentication.

[fabienthetis]

With php library, it is the solution.
Example of query:
$cred = $connection->get("/statuses/user_timeline", array(“screen_name” => “twitterapi”, “count” => “2”));

[c-w-n]

I am having this exact same issue with a Rest Api in C#. All calls authenticate properly until including something such as an emoji or a non-ascii character. Below is an example (Top lines represent the test’s from Twitters Oauth Tester). The post status is status=æ http://something.com etc.

Signature base string 	POST&https%3A%2F%2Fapi.twitter.com%2F1.1%2Fstatuses%2Fupdate.json&oauth_consumer_key%3Doauthconsumerkey%26oauth_nonce%3D7b1129a8aff79764ca16e7841d802a11%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1446137121%26oauth_token%3D3728392453-9rka5K8R9eN4Hinh09ocY0z5q0WRaqen79J720w%26oauth_version%3D1.0%26status%3D%25C3%25A6%2520https%253A%252F%252Fdev.app.com%252Fposts%252F00059382-dc28-4d7a-85e9-2de4edc68dd2
Signature base string	POST&https%3A%2F%2Fapi.twitter.com%2F1.1%2Fstatuses%2Fupdate.json&oauth_consumer_key%3Doauthconsumerkey%26oauth_nonce%3DI7OgYwsclSet2CJ0nvBfZpB1F9AjCKjY%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1446159566%26oauth_token%3D3728392453-9rka5K8R9eN4Hinh09ocY0z5q0WRaqen79J720w%26oauth_version%3D1.0%26status%3D%25C3%25A6%2520https%253A%252F%252Fdev.app.com%252Fposts%252Fd5904487-d0c0-407d-9338-e4de3b169f9e

Authorization: OAuth oauth_consumer_key="oauthconsumerkey", oauth_nonce="7b1129a8aff79764ca16e7841d802a11", oauth_signature="MkLXuCOxX8%2BE9kAHeEEKGP2o2JE%3D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1446137121", oauth_token="3728392453-9rka5K8R9eN4Hinh09ocY0z5q0WRaqen79J720w", oauth_version="1.0"
Authorization: OAuth oauth_consumer_key=\"oauthconsumerkey\", oauth_nonce=\"I7OgYwsclSet2CJ0nvBfZpB1F9AjCKjY\", oauth_signature=\"wPS4zalY3jSiRcq%2BOY4zhrvZjZY%3D\", oauth_signature_method=\"HMAC-SHA1\", oauth_timestamp=\"1446159566\", oauth_token=\"3728392453-9rka5K8R9eN4Hinh09ocY0z5q0WRaqen79J720w\", oauth_version=\"1.0\"

curl --request 'POST' 'https://api.twitter.com/1.1/statuses/update.json' --data 'status=%C3%A6+https%3A%2F%2Fdev.app.com%2Fposts%2F00059382-dc28-4d7a-85e9-2de4edc68dd2' --header 'Authorization: OAuth oauth_consumer_key="oauthconsumerkey", oauth_nonce="7b1129a8aff79764ca16e7841d802a11", oauth_signature="MkLXuCOxX8%2BE9kAHeEEKGP2o2JE%3D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1446137121", oauth_token="3728392453-9rka5K8R9eN4Hinh09ocY0z5q0WRaqen79J720w", oauth_version="1.0"' --verbose				
curl -v -X POST -H \"Content-Type: application/x-www-form-urlencoded\" -H \"Accept-Language: en-us,en;q=0.5\" -H \"Accept-Encoding: gzip,deflate\" -H \"Accept-Charset: utf-8;q=0.7,*;q=0.7\" -H \"Authorization: OAuth oauth_consumer_key=\"oauthconsumerkey\", oauth_nonce=\"I7OgYwsclSet2CJ0nvBfZpB1F9AjCKjY\", oauth_signature=\"wPS4zalY3jSiRcq%2BOY4zhrvZjZY%3D\", oauth_signature_method=\"HMAC-SHA1\", oauth_timestamp=\"1446159566\", oauth_token=\"3728392453-9rka5K8R9eN4Hinh09ocY0z5q0WRaqen79J720w\", oauth_version=\"1.0\"\" https://api.twitter.com/1.1/statuses/update.json?status=%C3%A6%20https%3A%2F%2Fdev.app.com%2Fposts%2Fd5904487-d0c0-407d-9338-e4de3b169f9e%2Fuid%2F227951"

@episod can you provide any insight to this?