400 "{"errors":[{"message":"Bad Authentication data","code":215}]}

detour_ · 2013-06-05T21:47:35.000Z

This stackoverflow answer fixed the issue for me, Zend Framework (PHP): http://stackoverflow.com/a/16002174/16783

halmashossain · 2013-06-14T04:01:52.000Z

Same problem for me also

BTFDApp · 2013-06-17T10:26:57.000Z

I was able to solve the 400 error by sorting the oauth_xx parameters in the Authorization header alphabetically and I also removed the double quotes around the parameter names. I just looked at the differences with the request the OAuth tool generated at the dev.twitter.com web site and managed to figure it out.

The header should look like:


Authorization: OAuth oauth_consumer_key="xxx", oauth_nonce="xxx", oauth_signature="xxx", oauth_signature_method="HMAC-SHA1", oauth_timestamp="xxx", oauth_token="xxx", oauth_version="1.0"

vmoo7 · 2013-06-18T06:40:58.000Z

i am facing the same problem for
https://api.twitter.com/1.1/search/tweets.json?q=%23freebandnames&since_id=24012619984051000&max_id=250126199840518145&result_type=mixed&count=4
this url

and returning this result
{“errors”:[{“message”:“Bad Authentication data”,“code”:215}]}

please if some one got the solution please post over here. thanks in advance

teknotica · 2013-06-19T09:48:41.000Z

Hi Taylor,

Do you mind pasting an example of how the URL for searching will look like with all the Oath parameters needed? I think that will help a lot!

Thank you!

sanaimtiaz17 · 2013-06-24T06:35:20.000Z

hi, i am done with the twitter search API in january late, but due to the changes in API v1.1 my code is not working right now.
i am using the consumer key,secret key access key and access secret key and using the URL as given below:
"https://api.twitter.com/1.1/search/tweets.json?q=".$srchterm."&since_id=24012619984051000&max_id=250126199840518145&result_type=mixed&count=4"
but i didn’t get the right answer. Can you please help me out.
thanx in advance.

Sulabh_Jain · 2013-06-27T00:05:38.000Z

Was this resolved, I am getting the same payload

{“errors”=>[{“message”=>“Bad Authentication data”, “code”=>215}]}

shagun008 · 2013-06-27T17:35:17.000Z

hi guys,
new to twitter dev.
trying to use https://api.twitter.com/1.1/statuses/mentions_timeline.json?count=2&since_id=14927799 in the browser.
getting error : {“errors”:[{“message”:“Bad Authentication data”,“code”:215}]}

Can anyone help ?

Regards,
Shagun

Passion_beat · 2013-06-30T16:24:36.000Z

I am facing the same issue can u help me???

Passion_beat · 2013-06-30T16:25:57.000Z

I am facing the same issue…I am using PHP…can anyone help me???

roseemmons · 2013-07-16T23:37:07.000Z

Hrm. Having the same problem. Can’t even get Twitter’s example code to work. What did I do wrong? Thank you in advance for the help!

whitelight007 · 2013-07-17T11:27:54.000Z

getting the same thing please let me know also looking at this thread. if this really is an issue and not a fault at the users end who is trying to retrieve data using 1.1 api then twitter needs to handle this ASAP.

yehenrytian · 2013-07-17T14:15:00.000Z

The new REST v1.1 search API is not working, I am using PHP, just updated to 1.1 yesterday, everything else seems fine, except for search, the example from the dev website does not work:
$xml = $twitter->http(‘https://api.twitter.com/1.1/search/tweets.json?q=%40twitterapi’);

I am using PHP. Array ( [errors] => Array ( [0] => Array ( [message] => Bad Authentication data [code] => 215 ) ) )

Here is my work: http://pintweet.tk

episod · 2013-07-17T14:44:39.000Z

Make sure that the library you’re using is doing the right thing for you on the encoding of characters. It may over-encode if you pre-encode. API v1.1 is much stricter about only accepting valid encodings – in query strings, POST bodies, or the OAuth signature base string. Dig deeper into what your code is doing to understand how the request is actually being formulated.

yehenrytian · 2013-07-17T18:03:00.000Z

I don’t think it is a string encoding issue. I used to use the old search api, and it works fine:

$xml = $twitter->http(‘http://search.twitter.com/search.json?q=hello&rpp=5&page=2’, ‘GET’);

I think it is something wrong with the search API itself, or we will not get: Bad Authentication data [code] => 215

episod · 2013-07-18T14:56:02.000Z

The old Search API didn’t support require OAuth but API v1.1 does – are you not sending authentication credentials with your request?

malcomcc · 2013-07-19T10:49:09.000Z

I’ve had the same problem just 15 minutes before.
I’ve looked for an answer that works properly but I haven’t found anything right.
Now I already fixed
It’s not a string encoding issue. It just a string issue, more exactly the quotes. At least for me.
I’m using abraham’s “twitteroauth” and i’ve notice that i was passing the four parameters (costumer_key,costumer_secret,oauth_key & oauth_secret) between quotes. I use variables to defines it and it treats them like strings. That’s was the problem.
I pull quotes out and everything works fine.
I hope it will be useful for all you.

vinayak57750874 · 2013-07-27T09:10:24.000Z

Hi,

Did you get the final working search URL? We are facing tough time to break this issue. Appreciate your early response

samiam84 · 2013-07-29T00:45:34.000Z

So instead of:

$consumer_key = "xxxxxxxxxxxx"
you used
$consumer_key = xxxxxxxxxxxx

?? I’m trying to solve the same problem,

thanks in advance!

JohnStudentay · 2013-08-01T09:02:00.000Z

I am getting this errror on using twitter api 1.1
{“errors”:[{“message”:“Bad Authentication data”,“code”:215}]}
while trying to access https://api.twitter.com/1.1/users/show.json?screen_name=xxx

Kindly resolve this asap or if there is an alternate then please share.