Twitter Timeline API: Pull Any Account at $0.04/1K

The Twitter timeline API is a set of REST endpoints that return a user's tweets as paginated JSON. TwitterAPIs exposes 47 endpoints across the X data surface, including four timeline-specific paths: user/tweets (originals only), user/tweets_and_replies (full activity), user/home_timeline (authenticated feed), and user/tweets/complete (auto-paginated full history). Every call costs $0.0008, so pulling 1,000 tweets costs $0.04 flat, with no subscription and no X developer account required.

user/tweets returns only the account's original posts, filtering out replies. user/tweets_and_replies returns the full chronological activity stream including both posts and replies. Use user/tweets when you want clean tweet-only data for brand monitoring or content analysis. Use user/tweets_and_replies when you need the complete picture of how an account engages, such as for sentiment analysis, conversation mapping, or full account audits.

No. TwitterAPIs uses a single Bearer token you copy from your dashboard after signup. There is no OAuth app review, no X developer account, and no waiting period. The only exception is user/home_timeline, which reads the authenticated user's own feed and therefore requires a user context token. For pulling any other public account's timeline, the standard Bearer key is all you need.

Yes. Use GET /twitter/user/tweets to get only the account's original posts. Replies, quote-tweets-as-replies, and thread continuations are stripped from the response. Each page returns about 20 original tweets at $0.0008 per call. If you need replies included, switch to user/tweets_and_replies on the same key.

Call GET /twitter/user/tweets/complete with the userName of the account. The endpoint auto-paginates through the entire history and returns all tweets merged into a single response, so you do not have to write cursor-loop logic yourself. For very large accounts with tens of thousands of tweets, use the standard user/tweets endpoint with manual cursor pagination instead: omit cursor on the first call, read the next_cursor from the response, pass it back on the next call, and repeat until has_more is false. Each page returns about 20 tweets and costs $0.0008.

Every call to any TwitterAPIs endpoint is $0.0008 (source: twitterapis pricing). The timeline endpoints return about 20 tweets per page, so pulling 1,000 tweets costs roughly $0.04. There is no monthly subscription and no minimum spend. You start with $0.50 in free credits after a 30-second signup with no card required, enough to pull around 600 tweets before you spend a cent. The official X API gates timeline access behind paid developer tiers with per-window tweet caps, making TwitterAPIs the cheapest managed path to high-volume timeline exports.

On your first request, omit the cursor parameter. The response includes a next_cursor string and a has_more boolean. Pass next_cursor back in the cursor parameter on your next call to fetch the following page. Repeat the loop until has_more is false. The same cursor pattern applies to user/tweets, user/tweets_and_replies, and user/home_timeline. user/tweets/complete handles the pagination internally and returns all pages merged, so no cursor loop is needed for that endpoint.

Yes. TwitterAPIs publishes an MCP server at @twitterapis/mcp that exposes all timeline endpoints as native tools. Any MCP-compatible AI agent or IDE can call user/tweets, user/tweets_and_replies, or user/tweets/complete directly, without writing HTTP request logic. See the MCP page for installation and usage instructions.