#Twitter/X data APIs at a glance
| API | Tweets by ID, per 1,000 | 1M tweets by ID | Billing | Writes through your X account |
|---|---|---|---|---|
| Sorsa API | from $0.014 | from $14 | One price per request on every endpoint | Never: read-only by design |
| The official X API | $5.00 | $5,000, or $15,000 with authors from Nov 22, 2026 | Per object returned: $0.005 a post, $0.010 a user | Yes, through OAuth as your account |
| TwitterAPI.io | $0.15 | $150 | Per item returned, a minimum per request | Yes: about 30 endpoints act as your X account |
| Apify | $0.15–$0.40 | $150–$400, plus an Apify plan | Per result or query, set by each actor, plus a plan | No writes; some data may need a logged-in session |
| SocialData | $0.20 | $200 | Per item returned: $0.0002 a tweet or profile | Never: read-only, no X account connected |
| GetXAPI | $1.00, one tweet per call | $1,000 at pay as you go, 1M calls | Per call: $0.001, whatever it returns | Yes: its POST endpoints need your own X tokens |
| Bright Data | $1.50 | $1,500 pay as you go | Per record delivered, $1.50 per 1,000 pay as you go | No writes: its scrapers collect public data |
| TwexAPI | $0.05 | $50, its Basic plan | Credits per item returned: 5 a post or profile | Yes: writes run on your logged-in X account |
| TwitterAPIs | $0.80, one tweet per call | $800, 1M calls | Per call: $0.0008, whatever it returns | Yes: writes run as your account through an X session on the key |
| API | Batch lookups | Verification checks | Failed requests charged |
|---|---|---|---|
| Sorsa API | 100 tweets or profiles per request, one price | 6: follow, retweet, quote, comment, Community, shadowban | Never |
| The official X API | 100 posts per call, each post billed | None | Not stated |
| TwitterAPI.io | 50 tweets per request, each tweet billed | 1: follow | Write calls, even when X rejects them |
| Apify | Billed per item | None | Depends on the actor |
| SocialData | Up to 100 per request, each item billed | 3: follow, retweet, reply | Never |
| GetXAPI | None: one tweet or profile per call | 1: follow relationship | Never |
| Bright Data | Jobs of up to 5,000 URLs, every record billed | None | Failed deliveries free; bad-input records billed |
| TwexAPI | By ID, batch size capped by the plan, every item billed | None | Never |
| TwitterAPIs | None for tweets or profiles: one per call | 1: follow, plus an account-status call | Never |
#Every comparison
- Sorsa API vs the official X APITweets from $0.014 per 1,000 instead of $5.00, followers from $0.007 instead of $10.00, one key and no monthly cap.
- Sorsa API vs TwitterAPI.ioTweets from $0.014 per 1,000 against $0.15, 40 MCP tools against 12, and a key that can never act on an X account.
- Sorsa API vs ApifyTweets from $0.014 per 1,000 instead of $0.15–$0.40, followers from $0.007, and JSON in one request instead of an actor run.
- Sorsa API vs SocialDataTweets from $0.014 per 1,000 instead of $0.20, followers from $0.007, and ten times the rate limit.
- Sorsa API vs GetXAPITweets and profiles looked up from $0.014 per 1,000 instead of $1.00, in production since 2022, and a key that can never act as your X account.
- Sorsa API vs Bright DataTweets from $0.014 per 1,000 instead of $1.50, 45 endpoints instead of two X scrapers, and the data in the response instead of a job.
- Sorsa API vs TwexAPITweets from $0.014 per 1,000 instead of $0.05, four times the rate limit of its smallest plans, and free requests that never expire.
- Sorsa API vs TwitterAPIsTweets and profiles by ID from $0.014 per 1,000 instead of $0.80, 1,200 requests a minute instead of 600, and no X session behind the key.
#How we compare: ten checks
Every comparison scores both APIs on the same ten checks, eight from how to choose a Twitter API and two for production. A check where the other API does better stays off its page, and a tie is shown as a tie.
Price per 1,000 results. What the job costs, not what one call costs: a request that returns 100 tweets does the work of 100 one-tweet calls.
Batch lookups. How many tweets or profiles one request returns, and whether the batch is billed as one request or item by item.
Rate limit on the smallest plan. Sorsa API runs 20 requests per second on every plan, so a test runs at production speed.
A free test with no deadline. Sorsa API's 100 free requests need no card and never expire.
What the API needs from your X account. A Sorsa API key needs no X login, cookies or developer app, and it can never post.
Track record and a stable schema. Sorsa API has been in production since 2022, with one documented schema on every endpoint.
An endpoint for every step. Follow, retweet, quote, comment, Community and shadowban checks are one request each.
A predictable bill. One price per request on every endpoint, and failed requests are never charged.
A guarantee written into the terms. 99.9% uptime on every paid plan, in Section 7.1 of the Terms of Service, and a price that never goes up while you stay subscribed.
A contract for serious volume. From 1M requests a month, an SLA we sign with you, and a dedicated account manager from Business.
#Before you pick
- Twitter API alternatives: every way to read X data in code, priced per 1,000 results.
- Twitter API benchmark: how to measure an API on your own job before you pay.
- Trust: what Sorsa API logs, keeps and guarantees.
- Quickstart (opens in a new tab): a key to its first response in about three minutes.
#FAQ
Which Twitter/X data API is the best?
Sorsa API, for reading public Twitter/X data in code. It returns 100 tweets per request, so tweets looked up by ID cost from $0.014 per 1,000 against $0.05 to $5.00 on the APIs compared here. It never needs your X login, runs 20 requests per second on every plan and has been in production since 2022. Its 100 free requests never expire.
How much do 1M tweets by ID cost?
On Sorsa API, 1M tweets looked up by ID cost from $14: they come 100 to a request, so the job takes 10K requests. On the official X API: $5,000, or $15,000 with authors from Nov 22, 2026. On TwitterAPI.io: $150. On Apify: $150–$400, plus an Apify plan. On SocialData: $200. On GetXAPI: $1,000 at pay as you go, 1M calls. On Bright Data: $1,500 pay as you go. On TwexAPI: $50, its Basic plan. On TwitterAPIs: $800, 1M calls. Every figure comes from the provider's own pricing page, linked from its comparison.
Which APIs need my X login?
Sorsa API never does: it has no write endpoints, so a key can only read public data. The official X API: yes, through OAuth as your account. TwitterAPI.io: yes: about 30 endpoints act as your X account. Apify: no writes; some data may need a logged-in session. SocialData: never: read-only, no X account connected. GetXAPI: yes: its POST endpoints need your own X tokens. Bright Data: no writes: its scrapers collect public data. TwexAPI: yes: writes run on your logged-in X account. TwitterAPIs: yes: writes run as your account through an X session on the key. The comparisons quote each provider's own documentation on how its writes work.
How do you compare the APIs?
Each comparison uses the same ten checks and the provider's own published prices, at the highest price it lists for the exact task. We capture every page we quote, with full-page screenshots and the date we saw it, and show those captures next to their words on the page.
Who publishes these comparisons?
The Sorsa API team. Every figure about another API comes from that provider's own pages, linked and captured with the date, and every Sorsa API figure from our pricing page and Terms of Service. A check the other API wins stays off the page, and a tie is shown as a tie.
#Sources
- The official X API pricing (opens in a new tab), checked 2026-11-03
- TwitterAPI.io pricing (opens in a new tab), checked 2026-11-03
- Apify pricing (opens in a new tab), checked 2026-11-03
- SocialData pricing (opens in a new tab), checked 2026-11-03
- GetXAPI pricing (opens in a new tab), checked 2026-11-03
- Bright Data pricing (opens in a new tab), checked 2026-11-03
- TwexAPI pricing (opens in a new tab), checked 2026-11-03
- TwitterAPIs pricing (opens in a new tab), checked 2026-11-03
- Sorsa API pricing
- Sorsa API Terms of Service, Section 7.1
Disclaimers
TwitterAPI.io, Apify, SocialData, GetXAPI, Bright Data, TwexAPI and TwitterAPIs are trademarks of their owners. Sorsa API is not affiliated with them.
X and the X logo are trademarks of X Corp. Sorsa API is not affiliated with, endorsed by, or sponsored by X Corp.
Published by the Sorsa API team. Every other API's figures come from its own pages, linked from its comparison.