Documentation Index
Fetch the complete documentation index at: https://docs.x.com/llms.txt
Use this file to discover all available pages before exploring further.
Retweets lookup: Standard v1.1 compared to X API v2
If you have been working with the standard v1.1 v1.1 GET statuses/retweets/:id, v1.1 GET statuses/retweets/:ids, the goal of this guide is to help you understand the similarities and differences between the standard v1.1 and X API v2 Retweets lookup endpoints.- Similarities
- Authentiation
- Users per request limits
- Differences
- Endpoint URLs
- Request limitations
- App and Project requirements
- Response data format
- Request parameters
Similarities
Authentication Both the standard v1.1 and X API v2 Retweets lookup endpoints (v1.1 GET statuses/retweets/:id and v1.1 GET statuses/retweeters/:ids) use OAuth 1.0a User Context or OAuth 2.0 Bearer Token. Users per request limits For both v1.1 and v2 GET endpoints the max number of users that will be returned by the Retweets lookup endpoint is 100 users. For the v2 Retweets lookup endpoint, there is no pagination token being passed, by default we give out 100 users and that’s the max that is returned.Differences
Endpoint URLs- Standard v1.1 endpoints:
- https://api.x.com/1.1/statuses/retweets/:id.json (Returns a collection of the 100 most recent