#1

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

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

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

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

If I remove the hash tag component “%23” I get back a bunch of results in json format, but they are not screened by hash tag and therefore of very little use. They often includes screen names and other information.

#2

Also tried &include_entities=true, that doesn’t appear to work either.

#3

Verify your OAuth and HTTP implementations. API v1.1 is strict in its requirements with properly formed HTTP and OAuth requests. It’s likely that the encoding on your “#” is being munged before it reaches Twitter.