Tweets & Engagement
/v1/tweet/info returns one tweet with all of its metrics, media and author object. If you have more than a couple of tweet IDs, use /v1/tweets/batch instead — it takes up to 100 IDs in a single request. In production testing, 30 tweets took 0.77 seconds through the batch endpoint versus 9 seconds looping single lookups, and it costs one quota unit instead of 30.
For conversations, /v1/tweet/replies returns the reply tree and /v1/tweet/thread reconstructs a multi-tweet thread in order. /v1/tweet/quotes finds who quote-tweeted a post and what they said — useful when a quote storm matters more than the replies.
The composite endpoints do several fetches internally and return one object: /v1/user/whois for account due-diligence, /v1/tweet/engagement for an interaction summary, /v1/batch/user_info for up to 100 profiles at once. They exist to save you round trips, and they're priced below what the same calls would cost separately.
Note that X restricts liker data, so there is no likers endpoint — /v1/tweet/retweeters is available and returns full profiles.
Tweet Details
Full tweet with all metrics and author.
{ "status": "success", "data": {
"id": "2078...", "text": "...", "like_count": 109,
"retweet_count": 17, "view_count": 45152,
"author": { ... } } }Replies
Replies to a tweet.
{ "status": "success", "data": [ ...replies ] }Full Thread
The complete thread in chronological order.
{ "status": "success", "data": [ ...thread tweets ] }Retweeters
Users who retweeted (paginated).
{ "status": "success", "data": [ ...users ], "meta": { "next_cursor": "..." } }Whois Due-Diligence
One call: profile + account transparency (based-in, connected-via, username changes) + recent tweets. Concurrent.
{ "status": "success", "data": {
"profile": { ... },
"about": {
"account_based_in": "United States",
"connected_via": "United States App Store",
"username_changes": 0, ...
},
"recent_tweets": [ ... ] } }Engagement Panorama
One call: retweeters + replies. Concurrent aggregation.
{ "status": "success", "data": {
"retweeters": [ ... ],
"replies": [ ... ] } }Batch Profiles
Up to 100 profiles in one concurrent call.
{ "status": "success", "data": [ ...profiles ],
"meta": { "count": 3 } }Batch Tweets
Up to 100 tweets in one request — ~70x faster per tweet than looping single lookups.
{ "status": "success", "data": [ /* tweets */ ],
"meta": { "count": 100, "requested": 100, "missing": 0 } }Quote Tweets
Who quoted this tweet and what they said. X's index favours recent content.
{ "status": "success", "data": [ /* quote tweets */ ],
"meta": { "count": 20 } }