Is http://search.twitter.com/search.json?q=searchterm being deprecated?


#1

Is http://search.twitter.com/search.json?q=searchterm being deprecated?

It seems that the help page makes no mention of it - and the search function within the REST api (api.twitter.com) is the one which is being deprecated.

Please clarify!

Thanks,
James


#2

The unofficial v1-ish /1/search.json method on api.twitter.com was separately deprecated from the rest of API v1.

search.twitter.com is being deprecated on the same schedule as API v1 – meaning in March 2013, search.twitter.com/search.json will cease functioning.

You’ll need to use API v1.1’s /1.1/search/tweets.json method instead.


#3

The following OAuth authorized request doesn’t appear to work:

= %23, does not appear to work, returns 0 results. The old API was capable of searching on hash tag and now it’s not.

https://api.twitter.com/1.1/search/tweets.json?q=%23AACR

Is there some reason we wouldn’t be able to search on a hash tag? Seems like a necessary component of the search functionality.


#4

It’s possible the library that you are using is mis-encoding the escaped “#” symbol by the time it is actually sent to our API. Verify your entire request path and make sure that it’s sending what you actually expect it to send, and that your OAuth signature base string also has the right amount of escaping. I have no issues making this request and getting results.