Search/twees invalid results as compared to twitter.com/search


#1

Hi all,

Can you please advise why are we getting very limited results for search/tweets:
https://api.twitter.com/1.1/search/tweets.json?q=iamyoursjesus&result_type=mixed&count=100

Versus:
https://twitter.com/search?f=realtime&q=%23iamyoursjesus&src=typd

The REST API endpoint always returns 2 “recent” results for this particular search (verified on APIGEE), while the search on twitter returns a page
"#iamyoursjesus" is reported by one of our clients who is experiencing the issue.


#2

This is explained in the documentation. The index used by the Search API is optimised for recency and only covers the past 7-10 days.

It allows queries against the indices of recent or popular Tweets and behaves similarily to, but not exactly like the Search feature available in Twitter mobile or web clients, such as Twitter.com search.

Before getting involved, it’s important to know that the Search API is focused on relevance and not completeness. This means that some Tweets and users may be missing from search results.