Hello,
I was trying to get all the retweeters from one of my tweets. I assume there is no cursor available on the API v2 since it doesn’t show in the meta block but what is bugging me most is the 41 results count in the meta whereas I have 779 retweets on that post.
Some other posts of mine beyond 100 RTs give 90 or less in the results.
Why such differences between the API and the plain results in the Twitter app? Is there any pagination fixed limit ( like 100 or so) that should be at least visible on my posts over 100 RTs?
NB : Working with Postman to manage the curl requests.
NB2 : here is the tweet id if you want to test it by yourself => 1402960414959341570
Thanks for reaching out. So the retweeted_by endpoint will return 100 most recent Retweets but this can return some strange results from time to time. This is actually an issue we’ve been aware of a while and has to do with a sort of “cache” of available Tweets/Retweets that our team can pull.
For both the Twitter app and the API, in some cases, Retweets are still Retweeted but may not show in the results, and it can be hard to pull a full list or see your Retweet in a list. The reasoning is based on the timing of the Retweet of the Tweet or the number of Retweets since the Tweet has been Retweeted. Our team has been engaging closely with other teams at Twitter to look for a more robust solution. I’ll be sure to let you know if I hear of anything further.
2 Likes
Thank you for your answer, I’m looking forward to your investigations.
Cheers,