twitterapi.io and TwittrAPI both sell access to X data without an X developer account, both take an API key in a header, and both cover users, tweets, search, lists, communities and trends. The main differences are the billing unit, the response format and a few endpoints that only one of us has.
We run TwittrAPI. twitterapi.io details below come from its own pages: prices, limits, free credit and free tools checked on 12 October 2026, account monitoring on 13 October 2026, docs details on 10 October 2026. Each number links to its source.
At a glance (as of October 2026)
X-API-KEY headerX-API-Key headercursor in, bottom cursor inside X's JSONcursor in, next_cursor and has_next_page outThe twitterapi.io homepage also mentions "1,000+ req/s"as of Oct 2026 and its docs "up to 200 QPS per client"as of Oct 2026; the table uses its dedicated limits page.
Price: per call vs per tweet
Single lookups. One tweet by ID or one profile is one call on both services. twitterapi.io has a minimum of $0.00015 per callas of Oct 2026, so 1,000 lookups cost at least $0.15 per 1,000 callsas of Oct 2026. On TwittrAPI they cost $0.065 to $0.09, depending on your tier.
Batch profiles. We return up to 100 profiles per call to GET /user/users/by/ids, so 1,000 profiles take 10 calls ($0.00065 to $0.0009). twitterapi.io charges 1 credit per profile when a batch returns 100 or more ($0.01 per 1,000)as of Oct 2026.
Timelines and search. twitterapi.io returns up to 20 tweets per pageas of Oct 2026. Our count defaults to 20, but X decides how many come back. If a page holds 20 tweets, 1,000 tweets cost $0.15 per 1,000 tweetsas of Oct 2026 on twitterapi.io and $0.00325 to $0.0045 on TwittrAPI (50 calls). Treat that as an estimate and measure with your queries.
Followers. twitterapi.io returns up to 200 per callas of Oct 2026 at its lowest per-item rate, from $0.01 per 1,000as of Oct 2026. How many followers we get per call depends on what X returns for your count, so test it.
Account monitoring: every account, any size
Both of us watch X accounts for you and push their new tweets to a webhook. The difference is which accounts get the fast lane.
twitterapi.io: on its stream page, the low-latency path covers authors with 5,000+ followers (moving to 2,000+)as of Oct 2026. For other accounts it says accounts below that may first arrive through the standard path, with no latency stated for itas of Oct 2026. On the fast path it reports 50% of tweets under 500 ms, 80% under 1 sas of Oct 2026. Plans start at $29/month for 6 accounts, extra accounts $5/month eachas of Oct 2026; the largest listed is $999/month for 2,000 accountsas of Oct 2026.
TwittrAPI: no follower minimum: every public account is checked at its plan's guaranteed interval. A niche account with 50 followers is checked as often as one with 5 million. Plans start at $19/month for 10 accounts (Real-time, checked at least every 1 s) and $5/month for 10 accounts (Standard, checked at least every 60 s), up to $1,999/month for 5,000 accounts (Real-time, checked at least every 1 s). Every event carries the tweet's time and the time we saw it, so you can measure the latency yourself (monitoring docs, plans and a side-by-side comparison).
The two are built differently: twitterapi.io describes a push stream and states delivery percentiles, we state the interval we check at. If your accounts are large, compare the latency you measure on both. If you watch small accounts (new projects, local news, founders, competitors' staff), the follower threshold matters, and we have none.
Where twitterapi.io is the better fit
- Readable JSON out of the box. Tweets come as flat objects with
likeCount,createdAtand the author inside. Our responses are X's own JSON, which has more fields but needs a parser. - Endpoints we do not have: Space details, a dedicated mentions endpoint, follower ID lists of up to 5,000 follower IDs per callas of Oct 2026, thread context, and webhook or websocket filter rules on search queries (our monitoring watches accounts, not queries).
- Higher limits on big plans: 500 requests/s (Business plan)as of Oct 2026.
- More write actions, such as DMs and profile updates, for teams that automate their own accounts (like ours, these need the account's login cookies and a proxy).
- More free credit to start: $1 credit for new accounts, no card requiredas of Oct 2026, against $0.10 on a new TwittrAPI account.
- Card payment through Stripe.
Where TwittrAPI is the better fit
- Monitoring small accounts: no follower minimum: every public account is checked at its plan's guaranteed interval, against a fast lane for the low-latency path covers authors with 5,000+ followers (moving to 2,000+)as of Oct 2026 on twitterapi.io. Our smallest Real-time plan is $19/month for 10 accounts (Real-time, checked at least every 1 s); twitterapi.io starts at $29/month for 6 accounts, extra accounts $5/month eachas of Oct 2026.
- Lookups and batch lookups, because a call costs the same whatever it returns.
- Higher limits on small accounts: 30 requests/s after the first top-up and 3 on the trial key, against 20 requests/s after payingas of Oct 2026 after paying and 0.2 requests/s before the first paymentas of Oct 2026.
- No credit that runs out. Everything you top up stays until you use it. On twitterapi.io recharged credits do not expire either, but bonus credits do (recharged credits do not expire; bonus credits expire after 30 days (31 on the pricing page)as of Oct 2026).
- Crypto without a fee (USDT or USDC on Polygon, USDT on Tron, or Litecoin).
- Refunds on 400, 408, 409 or 5xx responses, shown in the
X-Refundedheader. - Endpoints twitterapi.io's docs index does not list: a user's media timeline (
GET /user/{userId}/media), handle-to-ID conversion for up to 100 handles in one call (GET /user/usernames/to/ids), account status for up to 500 handles per call (GET /user/usernames/status), and job listings (GET /jobs/search/{searchTerm}). - Integrations: SDKs for Python, Node.js and Go, an MCP server for AI agents, an n8n node and LangChain and LlamaIndex tools (integrations).
- Marketplaces: you can also buy through RapidAPI or JojAPI if your company pays for APIs there.
Endpoints side by side
GET /twitter/spaces/detailThe full mapping with parameters is in the migration guide. Our endpoint reference is in the docs.
Free tools
Both of us have free tools on the website. twitterapi.io lists 4 free tools: shadowban check, follow checker, video downloader, tweet ID to dateas of Oct 2026. We have 6 free tools: Tweet ID to date, Twitter user ID finder, Follower count checker, Thread reader, Tweets to CSV, Shadowban checker, at /tools. The tools are for single lookups; for anything regular you need an API key on either service.
How to decide
Take three or four queries you really run. Sign up at /start for the $0.10 test credit and run them here, and on twitterapi.io with its own free credit. Write down calls, items returned and cost, then compare cost per 1,000 items. For pure lookups the published prices already answer it; for lists and search only your own numbers will.
TwittrAPI is not affiliated with X Corp. Reading data needs no X account; optional account actions use your own X session cookie and proxy.
Frequently asked questions
Is TwittrAPI cheaper than twitterapi.io?
For single lookups, yes on published prices: 1,000 single-tweet lookups cost $0.065 to $0.09 on TwittrAPI and at least $0.15 per 1,000 callsas of Oct 2026 on twitterapi.io, which has a minimum of $0.00015 per callas of Oct 2026. For batch profile lookups and follower lists twitterapi.io has volume rates from $0.01 per 1,000as of Oct 2026, so compare with your own workload.
Which one gives more free credit?
twitterapi.io: $1 credit for new accounts, no card requiredas of Oct 2026, after an invisible bot check, one per person and network ($0.10 if the same IP signed up within 30 days); expires after 31 daysas of Oct 2026. TwittrAPI: $0.10 for new direct accounts, valid 14 days, which is about 1,100 calls. twitterapi.io gives more.
Does twitterapi.io or TwittrAPI have higher rate limits?
twitterapi.io lists 20 requests/s after payingas of Oct 2026, 50 requests/s (Scale plan)as of Oct 2026 and 500 requests/s (Business plan)as of Oct 2026. TwittrAPI gives 30 requests per second after the first top-up, with booked tiers of 50 to 1,000 and 3,000 on request.
Does twitterapi.io only monitor accounts with many followers?
Not only, but the fast lane depends on it: the low-latency path covers authors with 5,000+ followers (moving to 2,000+)as of Oct 2026, and accounts below that may first arrive through the standard path, with no latency stated for itas of Oct 2026. On TwittrAPI there is no follower minimum: every public account is checked at its plan's guaranteed interval, from $19/month for 10 accounts (Real-time, checked at least every 1 s).
Is the response format the same?
No. twitterapi.io returns its own flat camelCase objects with the author inside each tweet. TwittrAPI passes X's own JSON through. Plan an adapter when you switch; the migration guide has one.
Do I need an X developer account for either?
No. Both issue their own API keys.