X · Tweets
Tweets
Three ways to read posts, each with its own endpoint
01
Which one you want
Three endpoints and not one, because they are three parsers. What a search hands back, what a timeline hands back and what a single post hands back are different shapes — one endpoint answering any of them would be one you could not write against.
| /x/tweets/search | 3 a post | any advanced search, run as Latest |
| /x/tweets/handle | 3 a post | one account's posts, with its header |
| /x/tweets/url | 12 | one post, and the replies that came with it |
The post itself is the same shape everywhere — a search result, a timeline entry and a reply are the same card. What differs is what wraps it, and the pages below say what.
Feeds return one page per call at three credits per returned post. Pass the response’s pagination_token to continue. A single post costs twelve credits, including its first response’s direct replies.
next
Search Tweets →
Any advanced search X understands, and the operators that still work.
next
User Tweets →
One account's posts, with the profile header and the exact follower count.
next
Tweet →
A single post, its engagement counts and direct replies.