QUICKSTART
How to Start With the TwitterAPIs API
You need one Bearer key and a single HTTP call. Sign up, copy the key, and send a GET to tweet/advanced_search with an Authorization: Bearer header. No X developer account, no review queue, no card. New accounts start with $0.50 in free credits, and your first read call costs $0.0008.
Quick answer
The TwitterAPIs API is a hosted Twitter and X data API you call with one Bearer key and a single HTTP request, with no X developer account or approval queue. To start, sign up, copy your key from the dashboard, and send a GET to tweet/advanced_search with an Authorization: Bearer header. Every new account includes $0.50 in free credits and the first read call costs $0.0008.
Your First Call, in One Line
Swap $TWITTERAPIS_KEY for the key in your dashboard. This searches recent tweets and returns a page of about 20 results.
1curl "https://api.twitterapis.com/twitter/tweet/advanced_search?query=from%3Anaval%20min_faves%3A1000&product=Latest" \2 -H "Authorization: Bearer $TWITTERAPIS_KEY"A 200 returns JSON with a tweets array and a next_cursor. A 401 means the key is wrong or missing; re-copy it and check the header.
Get a key
Sign up with Google or email. Your Bearer key exists right away, with no developer account, no review queue, and no card. Every new account starts with $0.50 in free credits, enough for around 625 read calls.
Make your first call
Send a GET to tweet/advanced_search with your key in the Authorization header. That single curl line returns a page of matching tweets.
Port it to your stack
The same request runs in Python (requests) or JavaScript (fetch). There is no SDK to install; it is plain HTTP with one header.
Read the response
Each read call returns roughly 20 tweets in a tweets array plus a next_cursor. Pass the cursor back to page through more results.
Step 1: Mint Your Bearer Key
Log in with Google in half a minute and your personal key appears in the dashboard. No developer account, no waiting line, no card. You land $0.50 in free credits at signup.
The Same Call in curl, Python, and JavaScript
There is no language SDK to install. Every endpoint is plain HTTP with one Bearer header, so it works from any runtime. Here is the same advanced-search request three ways.
1curl "https://api.twitterapis.com/twitter/tweet/advanced_search?query=from%3Anaval%20min_faves%3A1000&product=Latest" \2 -H "Authorization: Bearer $TWITTERAPIS_KEY"The Bearer header matches the official X API shape, so client code written against api.x.com runs here after one base-URL change to api.twitterapis.com.
Read the Response and Page Further
A read call returns roughly 20 tweets per request inside a tweets array, plus a next_cursor string. To fetch the next page, send the same request again with cursor set to that value. Stop when the array comes back empty.
Need a single profile instead of a search? Call user/info?username=naval, also a $0.0008 read. The full endpoint reference, with every parameter and response field, lives in the API docs.
What It Costs After the Free Credits
Standard reads and simple write actions are $0.0008 per call (about $0.04 per 1,000 tweets). A few endpoints are premium: creating a tweet and the two DM reads are $0.0016, full account history (user/tweets/complete) is $0.0024, and a full thread expansion (tweet/thread) is $0.004. That is the whole price list across all 47 endpoints.
See the full breakdown on the pricing page, read how the key itself works in the Twitter API key guide, wire your key into an AI agent with the MCP server, or see how the catalog stacks up in TwitterAPIs vs twitterapi.io.
Frequently Asked Questions
A standard read call, like tweet/advanced_search or user/info, costs $0.0008 and returns about 20 tweets, which works out to $0.04 per 1,000 tweets (source: twitterapis pricing). Every new account starts with $0.50 in free credits, so your first call (and roughly 625 more) is covered before you ever add a card.
One Bearer token. Every request carries a single Authorization: Bearer YOUR_API_KEY header, the same shape as the official X API Bearer token. There is no OAuth 1.0a pair and no PKCE handshake to manage for data reads.
Write actions are POST requests with the same Bearer header. Simple writes (like, retweet, bookmark, follow, their undos, and delete) bill at the standard $0.0008 per call. Creating a tweet (tweet/create) is a premium write at $0.0016 per call. A like, for example, is a POST to tweet/favorite with a JSON body of {"tweet_id": "..."}.
No. TwitterAPIs issues your key the moment you sign up with Google or email. There is no developer account at console.x.com, no use-case writeup, and no approval queue. You go from signup to a working call in under a minute.
There are no platform-level rate caps by default, so you will not hit the per-endpoint 15-minute and daily windows the official X API enforces. You can set your own per-endpoint caps if you want a spend ceiling; without them, a 429 never fires.
Read endpoints return roughly 20 tweets per call inside a tweets array, alongside a next_cursor string. To fetch the next page, send the same request again with the cursor parameter set to that value. Keep paging until the array comes back empty.
Next read
Continue exploring related pages:
Twitter API use cases
14 use cases from sentiment analysis to lead generation.
Twitter timeline API
Pull an account's full posting history over one REST endpoint.
Twitter list API
Read list members and list timelines with the same Bearer key.
TwitterAPIs pricing
Brand pricing page with endpoint-level costs and quick totals.