Hey John, You need to URL encode (percent encode) the :) for this to work. If you are unsure how to form the search query I find using http://search.twitter.com/search first helps. When I do that and press search the correct encoding is displayed in the URL address bar.
For example, visit http://search.twitter.com/search and enter Twitter :) as the search term and click search The URL you'll end up with if you do this is: http://search.twitter.com/search?q=Twitter+%3A%29 To use this through the API simply add the format you want (json or atom) between the search and ?q. For example for json: http://search.twitter.com/search.json?q=Twitter+%3A%29 Hope that helps, Matt On Thu, Aug 26, 2010 at 4:37 AM, johnw <john.we...@gmail.com> wrote: > I'm trying to do some searches via the API and I have it working for > straight strings but when I try the emoticon syntax described here > (http://search.twitter.com/operators) for attitude I get this back > from the API: > code":17,"message":"No user matches for specified terms" > > e.g. "Twitter :)" returns the above message. > > I've tried to encode it via javascript before sending (encodeURI or > encodeURIComponent) but it does not help. > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en