How to know who favorite or rt a tweet?

tesisRecolector · 2017-01-25T04:52:10.597Z

I have a tweet.
I want to know which users make it a favorite tweet or RT it.
Thank you

SamiF1 · 2017-01-25T11:03:17.472Z

Using api rest see retweeted_status and favorite_count here https://dev.twitter.com/overview/api/tweets

andypiper · 2017-01-25T15:16:54.030Z

You’ll have to use the search API to find who might have retweeted a status. There’s no easy way to find out which users favourited a Tweet, but you can take a look at userstreams for the events.

richardhyland · 2017-01-25T16:15:33.898Z

doesn’t statuses/retweets/:id let you get who retweeted a status, but yes there’s no similar like endpoint.

DanielCHood · 2017-01-25T16:25:22.139Z

Only the most recent 100. In order to get all of them you have to do a bit more work.

andypiper · 2017-01-25T16:54:05.874Z

Right - I was summarising!

richardhyland · 2017-01-26T09:37:47.130Z

Indeed but there is cursoring isn’t there?

DanielCHood · 2017-01-26T13:13:09.606Z

No. The documentation is wrong about that.

Potential Issue with Statuses/Retweeters REST API

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)…

richardhyland · 2017-01-26T15:59:19.823Z

Seems to be very little point in having a count or cursor pagination on that endpoint then?

I can’t think of a good reason why that’s limited to 100 though? @andypiper

andypiper · 2017-01-26T16:06:27.328Z

Unfortunately I’m not sure of the history of that endpoint. I’d already made a note to myself that we need to fix the docs on this subject per @jcbl recent post about it. Unable to comment on whether this is a bug or by design without diving a lot deeper into the backend.