Potential Issue with Statuses/Retweeters

[DanielCHood]

I’m attempting to get the retweeters of a status, https://dev.twitter.com/rest/reference/get/statuses/retweeters/ids, and I believe there’s a problem unless I’m doing something wrong.

I’m using this tweet for my test case: https://twitter.com/CharlieDayQuote/status/794994090022563840. As you can see, there are plenty of retweets to warrant pagination but my response is only getting 93 retweeters and:

["next_cursor"] => int(0)
["next_cursor_str"] => string(1) "0"
["previous_cursor"] => int(0)
["previous_cursor_str"] => string(1) "0"

I’ve tried it both with suppressing the cursor variable and using cursor: -1.

PS, the docs indicate that you can specify a count field but that’s not covered in the expected parameters section.

Example Request
GET https://api.twitter.com/1.1/statuses/retweeters/ids.json?id=327473909412814850&count=100&stringify_ids=true

[jcbl]

@DanielCHood you can only get a maximum of 100 retweeters at all. It’s weird that the docs don’t emphasize this. I made a post about this a while back because it’s confusing, but nothing ever happened:

Paging is not possible with /statuses/retweeters/ids.json

(This is also available as a gist: https://gist.github.com/jeremylow/3e4d6b0a18370f7444bb84ccdc136f2d) Problem For endpoint /statuses/retweeters/ids.json, there is no way to page through ids returned by API. No combination of setting cursor or count parameters has any effect on return value of previous_cursor, next_cursor, etc. Documentation is here: https://dev.twitter.com/rest/reference/get/statuses/retweeters/ids Furthermore, although count parameter is honored, is not documented. I…

[DanielCHood]

Well that makes sense but the documentation should definitely be changed. Wish I could get more data but no big deal. Thank you.