Geo/search API not working on v1.1, with response {"message":"Bad Authentication data","code":215}


#1

Hi, I met the following issue when migrating to API v1.1:

geo/search API not working on v1.1, with response {“message”:“Bad Authentication data”,“code”:215}

while the same call works on v1.0.

Has anyone else met the same problem?


#2

What’s the URL you’re using to execute? Does it contain any reserved characters that you may need to encode? The HTTP & OAuth strictness level on 1.1 is higher.


#3

Actually I use the test url in the API doc
https://api.twitter.com/1.1/geo/search.json?query=Toronto
and
https://api.twitter.com/1.1/geo/search.json?query=Twitter%20HQ

I do the test both on PC browser (with a Twitter account logged in within the same browser) and Java twitter client, on PC browser I get the {“message”:“Bad Authentication data”,“code”:215} for both URLs (but API v1.0 works fine).

However, when I do the test on my test Java Twitter client, the first URL works fine, but the second URL returns 401 Unauthorized (while both works fine on API v1.0).


#4

Same issue… :frowning: