The endpoints described in this section are the replacements of the v1.1 endpoints that allow you to manage and lookup Retweets:
- GET statuses/retweets/:id
- GET statuses/retweeters/:ids
- POST statuses/retweet/:id
- POST statuses/unretweet/:id
If you are currently using any of these endpoints, you can use our migration materials to start working with the new v2 versions.
Learn more about the new Twitter API v2: Early Access.
Retweeting is one of the core features people use to engage in the public conversation on Twitter. With the Retweets lookup endpoints, you can see a list of accounts that Retweeted a given Tweet. In addition, the new manage Retweets endpoints allow you to Retweet a Tweet or undo a Retweet.
With the Retweets lookup endpoint, you can retrieve a list of accounts that have Retweeted a Tweet.
You can authenticate these endpoints with either OAuth 1.0a User Context or OAuth 2.0 Bearer Token. When authenticating, you must use keys and tokens from a developer App located within a Project. Learn more about getting access to the Twitter API v2 endpoints in our getting started page.
The manage Retweets endpoints enable you to Retweet or undo a Retweet of a specified Tweet on behalf of an authenticated account. For this endpoint group, there are two methods available POST and DELETE. The POST method allows you to Retweet a Tweet, and the DELETE method will enable you to undo a Retweet of a given Tweet.
Since you are making requests on behalf of a user, you must authenticate these endpoints with OAuth 1.0a User Context and use the Access Tokens associated with the user, which can be generated using the 3-legged OAuth flow. You can Retweet a Tweet from your account or an account of an authenticated user. With both endpoints, there is a user rate limit of 50 requests per 15 minutes per endpoint.