API v1.1 search/tweets truncating/limiting results


#1

Regards.
I’m experiencing some issues that are probably expected by still I’m not happy with the results:

I’m doing a search with the hashtag #obama (lots of results), and I want to return all tweets of the last 7 days (Today is Nov 01)

https://api.twitter.com/1.1/search/tweets.json?lang=es&count=100&result_type=recent&since=2013-10-25&q=%23obama

The thing is that I only get results down to 2 days ago. Not 7.

I get (updating the since_id value, of course), 8 responses with 100 statuses each, and 1 last response with only 99 statuses (and no [‘search_metadata’][next_results’] value). The “oldest” tweet I can get this was has only 2 days old.

NOW, if I add the &until=2013-10-26 parameter, it will return statuses of those dates (older statuses) but again, it will also limit the amount of total statuses I can request.

I understand there is a limit, and it’s logical, but I was expecting to get, at least, ALL tweets of the last 3 or 4 days, without an amount limit.

How can I force the api to loosen these limit, without the need of using ‘since’ + ‘until’ parameters on different requests (I want to only paginate)
What can you tell me about the ‘since’ parameter (which is not documented but actually working)?

It’s important to note that I’m not reaching the rate limit of the app. It’s not that.

Thanks


#2

We are seeing a similar issue, also when searching for ‘obama’.

When we don’t set a result_type parameter it appears to default to recent and only return approx 100 results.

When we set result_type=mixed we get approx 200 results.

My understanding was that the search API should return up to 1500 or 7 days worth of Tweets (whichever is hit first) and in previous testing and experience this seemed to be the case.

Has something changed? Are we misunderstanding the limitations of this part of the API?


#3

We are also seeing this and have been for months.


#4

hi, I have the same problem! I can get tweets of 1 day only, around 100 - 200 tweets for key word. Nice problem :frowning:


#5

Hello everyone,

Thank you for the reports. We have recently deployed some fixes related to search.

Please let us know if you are still encountering any issues with the results of this API endpoint.


#6

I am still seeing similar problem right now, I only get 1 day’s worth of tweets. Any update on this problem. Are you still seeing this?


#7

I’m still seeing this problem with my app http://appstore.com/magicanswers, but also using https://dev.twitter.com/console. No results for a hashtag search: https://api.twitter.com/1.1/search/tweets.json?q=%23magicanswers&result_type=recent&count=100&include_entities=true
(using my account via console and OAuth)
Is this going to be fixed soon?


#8

I should have included the results from the console tool (showing no results):

Using:
https://api.twitter.com/1.1/search/tweets.json?q=%23magicanswers&result_type=recent&count=100&include_entities=true

Response:
HTTP/1.1 200 OK
content-type:
application/json;charset=utf-8
x-frame-options:
SAMEORIGIN
x-rate-limit-remaining:
448
last-modified:
Tue, 17 Dec 2013 15:40:20 GMT
status:
200 OK
date:
Tue, 17 Dec 2013 15:40:20 GMT
x-transaction:
8f540a10ac0598ef
pragma:
no-cache
cache-control:
no-cache, no-store, must-revalidate, pre-check=0, post-check=0
x-xss-protection:
1; mode=block
expires:
Tue, 31 Mar 1981 05:00:00 GMT
x-rate-limit-limit:
450
set-cookie:
guest_id=v1%3A138729482018285786; Domain=.twitter.com; Path=/; Expires=Thu, 17-Dec-2015 15:40:20 UTC
content-length:
289
x-rate-limit-reset:
1387295654
server:
tfe
strict-transport-security:
max-age=631138519

{
“statuses”: [],
“search_metadata”: {
“completed_in”: 0.019,
“max_id”: 412970462902100000,
“max_id_str”: “412970462902099968”,
“query”: “%23magicanswers”,
“refresh_url”: “?since_id=412970462902099968&q=%23magicanswers&result_type=recent&include_entities=1”,
“count”: 100,
“since_id”: 0,
“since_id_str”: “0”
}
}


#9

Hi Am using search API and getting a single result whether i applied result per page 20.
Am using URL https://api.twitter.com/1.1/search/tweets.json?q=%23mystring


#10

try to remove %23 in the query