The 10 best Twitter (X) scrapers in 2026, priced and compared
We priced 10 Twitter (X) scrapers on November 18, 2026: hosted tools and other APIs charge $0.15 to $1.50 per 1,000 posts and Sorsa API from $0.07, while open-source libraries and browser extensions charge nothing but run on an X account.
Short answer: We priced 10 Twitter (X) scrapers on November 18, 2026. Hosted tools and other APIs charge $0.15 to $1.50 per 1,000 posts, while open-source libraries and browser extensions cost nothing but run on an X login, so that account carries the risk. To collect posts without risking an X account, use Sorsa API, a Twitter scraper API: POST /search-tweets returns about 20 posts per request from $0.07 per 1,000, and 100 free requests need no card.
- Endpoint
POST /search-tweets- Page size
- about 20 posts per request
- Price
- from $0.07 per 1,000
The 10 best Twitter scrapers at a glance#
We read each tool's own pricing page on November 18, 2026. The price is per 1,000 posts at the smallest published tier, and "X login" means the tool reads X through an X account, yours or one you supply. Each entry below links its source.
| Tool | Per 1,000 posts | X login needed | Output | Best for |
|---|---|---|---|---|
| 1. Sorsa API | from $0.07 by search, $0.014 by link or ID | No | JSON | Recurring collection in code, search back to 2006 |
| 2. TwitterAPI.io | $0.15 | No | JSON | Pay-as-you-go reads billed per tweet |
| 3. Apify Tweet Scraper V2 | $0.40 | No | JSON, CSV, Excel | No-code runs of 50 posts or more per query |
| 4. Bright Data | $1.50 | No | JSON, NDJSON, CSV | Posts by URL, delivered to cloud storage |
| 5. Octoparse | $0.30 | No | Excel, CSV, JSON, Google Sheets | No-code exports to a spreadsheet |
| 6. Oxylabs | $1.50 per 1,000 rendered pages | No | HTML, Markdown, AI-parsed JSON | Public x.com pages next to other sites |
| 7. twscrape | No fee; X accounts and proxies | Yes | Python objects, JSON lines | Developers who run a pool of X accounts |
| 8. Scweet | Free self-hosted; $0.25 to $0.30 hosted | Yes self-hosted, no hosted | CSV, JSON, Excel | Small Python jobs, or a hosted run |
| 9. twikit | No fee | Yes | Python objects | Old scripts, through the twifork fork |
| 10. Export Twitter Follower and TwExport | Free up to 150 rows per export, then Pro | Yes, your browser's X session | CSV | A one-off list of a few hundred rows |
1. Sorsa API
- Per 1,000 posts
- from $0.07 by search, $0.014 by link or ID
- X login needed
- No
- Output
- JSON
- Best for
- Recurring collection in code, search back to 2006
2. TwitterAPI.io
- Per 1,000 posts
- $0.15
- X login needed
- No
- Output
- JSON
- Best for
- Pay-as-you-go reads billed per tweet
3. Apify Tweet Scraper V2
- Per 1,000 posts
- $0.40
- X login needed
- No
- Output
- JSON, CSV, Excel
- Best for
- No-code runs of 50 posts or more per query
4. Bright Data
- Per 1,000 posts
- $1.50
- X login needed
- No
- Output
- JSON, NDJSON, CSV
- Best for
- Posts by URL, delivered to cloud storage
5. Octoparse
- Per 1,000 posts
- $0.30
- X login needed
- No
- Output
- Excel, CSV, JSON, Google Sheets
- Best for
- No-code exports to a spreadsheet
6. Oxylabs
- Per 1,000 posts
- $1.50 per 1,000 rendered pages
- X login needed
- No
- Output
- HTML, Markdown, AI-parsed JSON
- Best for
- Public x.com pages next to other sites
7. twscrape
- Per 1,000 posts
- No fee; X accounts and proxies
- X login needed
- Yes
- Output
- Python objects, JSON lines
- Best for
- Developers who run a pool of X accounts
8. Scweet
- Per 1,000 posts
- Free self-hosted; $0.25 to $0.30 hosted
- X login needed
- Yes self-hosted, no hosted
- Output
- CSV, JSON, Excel
- Best for
- Small Python jobs, or a hosted run
9. twikit
- Per 1,000 posts
- No fee
- X login needed
- Yes
- Output
- Python objects
- Best for
- Old scripts, through the twifork fork
10. Export Twitter Follower and TwExport
- Per 1,000 posts
- Free up to 150 rows per export, then Pro
- X login needed
- Yes, your browser's X session
- Output
- CSV
- Best for
- A one-off list of a few hundred rows
What a Twitter scraper does in 2026#
A Twitter scraper is a tool that collects public X data, such as posts, profiles and follower lists, by reading x.com's pages or replaying the requests x.com makes, instead of buying the data through an API. Our guide on how to scrape Twitter covers each way and what breaks it; this page prices the tools you would install or pay for.
Since X moved most of the site behind its login, a scraper's reach depends on whose account it uses. On November 2, 2026, x.com showed a logged-out visitor single posts and the first 9 posts of a profile, and sent search and follower lists to the login page.
Four kinds of tools do that work today:
- Browser extensions save what your own logged-in x.com tab shows as you scroll, so every page they read is a page your account opened, one screen at a time.
- Open-source libraries, such as twscrape and Scweet, replay x.com's internal requests with the cookies of X accounts you log in. They charge nothing and break each time X changes those requests.
- Hosted scraping tools and APIs, from actor stores to no-code templates, run the collection on their own servers and bill per result, from $0.15 to $1.50 per 1,000 posts. Apify's FAQ (opens in a new tab) says detailed follower lists need session cookies.
- Page-rendering scraping APIs fetch one public x.com page per request through proxies and hand back the page, so search results and follower lists stay out of their reach.
The 10 Twitter scrapers, priced one by one#
Each entry gives the price per 1,000 posts with its source, whether the tool needs an X login, what it hands back, what it suits best and what it costs you besides money. We priced and compared them from their own pages; we did not run a test of our own.
1. Sorsa API: a Twitter scraper API with no X login
Sorsa API is a Twitter scraper API: you send one key in the ApiKey header and get public posts, profiles and followers back as JSON, with no X login, cookies or proxies on your side. When X changes its site, the fix happens on Sorsa API's side and your code keeps working.
- Price per 1,000 posts: from $0.07 by search, about 20 posts per request, and from $0.014 by link or ID, 100 posts per request (pricing, November 18, 2026).
- X login needed: No.
- Output: JSON, with the author's full profile in every post.
- Best for: recurring or large jobs in code: search back to 2006, timelines, followers at 200 per request and profiles at up to 400 per request, at 20 requests per second on every plan.
- Trade-offs: you write a few lines of code, or use the free export tools; it is read-only, so it never posts, likes or follows, and it doesn't return who liked a post or anyone's bookmarks. The "from" prices are the largest plan's rate: on the $49 Starter plan (10,000 requests), search results work out to about $0.25 per 1,000 posts and lookups by ID to $0.049.
2. TwitterAPI.io: pay-as-you-go reads per tweet
TwitterAPI.io is a third-party X data API that bills each tweet it returns from a prepaid credit balance, with a key you get by signing in with Google.
- Price per 1,000 posts: $0.15 per 1,000 tweets, with a minimum of $0.00015 per request (pricing (opens in a new tab), November 18, 2026).
- X login needed: No: its own API key.
- Output: JSON.
- Best for: pay-as-you-go reads where billing per tweet suits the job.
- Trade-offs: every tweet is billed, so the bill follows the volume returned, and the free credits for new accounts, up to $1, expire after 31 days. Our Sorsa API vs TwitterAPI.io comparison goes through the rest.
3. Apify Tweet Scraper V2: no-code runs on Apify
Apify's Tweet Scraper V2, published by API Dojo in Apify's store, runs X searches and timelines on Apify's servers and bills per tweet.
- Price per 1,000 posts: $0.40 per 1,000 tweets, with at least 50 tweets per query (actor page (opens in a new tab), November 18, 2026). Free users get 5 runs a month of 10 items each, and no API access.
- X login needed: No; Apify's FAQ (opens in a new tab) adds that detailed follower lists need session cookies.
- Output: JSON, CSV or Excel, from the Apify console or its API.
- Best for: no-code runs on a schedule, wired into Apify's integrations.
- Trade-offs: the 50-tweet minimum per query, and a per-tweet bill that grows with the job: a million tweets cost $400. Sorsa API vs Apify compares the two in detail.
4. Bright Data: posts by URL, delivered to your storage
Bright Data's X scraper collects public posts and profiles from the URLs you give it and delivers them by API, webhook or cloud storage.
- Price per 1,000 posts: $1.50 per 1,000 records pay as you go; $499 a month for 384,000 records on its Scale plan, then $1.30 per 1,000; 5,000 free records a month (pricing (opens in a new tab), November 18, 2026).
- X login needed: No.
- Output: JSON, NDJSON, JSON lines or CSV, delivered to Amazon S3, Google Cloud Storage, Azure, Snowflake or SFTP.
- Best for: enterprise pipelines that start from post or profile URLs and land in a data warehouse.
- Trade-offs: the highest price per post on this list, for posts whose URLs you already have. In AIMultiple's benchmark (opens in a new tab), updated November 16, 2026, it averaged 7.6 seconds per X page and completed 99.9% of 1,000 requests. Sorsa API vs Bright Data has the full comparison.
5. Octoparse: Twitter templates for spreadsheets
Octoparse is a no-code scraping app with ready-made Twitter templates: by keyword or URL, by hashtag, for comments, and for followers and following.
- Price per 1,000 posts: $0.30 per 1,000 rows for its hashtag and comments templates, and no extra cost for the follower template (templates page (opens in a new tab), November 18, 2026), on top of an Octoparse account.
- X login needed: No, per Octoparse's FAQ.
- Output: Excel, CSV, XML, HTML or JSON, or straight into Google Sheets or a database.
- Best for: analysts who want rows in a spreadsheet without code.
- Trade-offs: the page publishes no price for its main keyword and URL template, and a template waits for Octoparse's fix after each change on x.com.
6. Oxylabs: public x.com pages through a scraping API
Oxylabs sells a general web scraping API with no X-specific product: you send an x.com URL, and it fetches the page through its proxies, renders it and returns the result.
- Price per 1,000 posts: $1.50 per 1,000 results for JavaScript-rendered pages on its smallest tier, falling to $1.22 past 2 million a month (pricing (opens in a new tab), November 18, 2026). One logged-out x.com page holds one post.
- X login needed: No, so it reaches only what x.com shows logged out: single posts and the top of a profile.
- Output: HTML or Markdown, or JSON through its AI parsing at $3.00 per 1,000 parsed pages.
- Best for: teams that already scrape other sites through Oxylabs and need some public x.com pages too.
- Trade-offs: no search results or follower lists, and you parse each page yourself or pay for parsing.
7. twscrape: open source, on X accounts you supply
twscrape is an open-source Python library that calls X's internal GraphQL API with the cookies of X accounts you add, so it reaches search, timelines and followers.
- Price per 1,000 posts: no fee; it runs on X accounts and proxies you supply (twscrape on PyPI (opens in a new tab), version 0.21.0 of November 6, 2026).
- X login needed: Yes: its README says it "requires authorized X/Twitter accounts".
- Output: Python objects, or JSON lines from its command line.
- Best for: developers who can run a pool of X accounts and update code after X's changes.
- Trade-offs: every account in the pool can be locked, and each change to X's internal requests breaks it until a release catches up.
8. Scweet: open source, or hosted with no account
Scweet is an open-source Python scraper that signs in with one auth_token cookie, and its author also runs it as a hosted actor on Apify.
- Price per 1,000 posts: free self-hosted; hosted, $0.25 to $0.30 per 1,000 result rows by Apify plan, plus a $0.006 start fee per run, with a 3,000-tweet free trial (Scweet on Apify (opens in a new tab), November 18, 2026).
- X login needed: Yes self-hosted, where its README (opens in a new tab) asks for a dedicated account, never a personal one; no for the hosted version.
- Output: CSV or JSON self-hosted; JSON, CSV or Excel hosted.
- Best for: small Python jobs, or a hosted run without an X account of your own.
- Trade-offs: self-hosted, the account behind the cookie carries the risk; its latest release is 5.8.2 of October 22, 2026.
9. twikit: broken upstream since March 2026
twikit is an open-source Python library that logs in to X as a normal user and calls the internal endpoints the x.com web app uses. Its latest release, 2.3.3 of February 7, 2025, fails on every call since X changed its web app on March 18, 2026: issue #408 (opens in a new tab), "Couldn't get KEY_BYTE indices", was still open on November 18, 2026. The community fork twifork (opens in a new tab) fixes that break and keeps the twikit import, but it signs in only with cookies from a browser session.
- Price per 1,000 posts: no fee (twikit on PyPI (opens in a new tab)).
- X login needed: Yes: a username and password upstream, browser cookies in twifork.
- Output: Python objects.
- Best for: keeping an old twikit script alive through twifork while you move it.
- Trade-offs: the upstream library doesn't work, and the fork runs on an account X can lock. Our guide to snscrape, Twint, twikit and twscrape alternatives maps each twikit call to one API request.
10. Export Twitter Follower and TwExport: the most-installed extensions
The most-installed X export extension we found in the Chrome Web Store on November 18, 2026 was Yue Apps' Export Twitter Follower (opens in a new tab), with 9,000 users. The same developer's TwExport (opens in a new tab), with 5,000 users, exports posts.
- Price per 1,000 posts: free up to 150 rows per export; more takes a Pro upgrade whose price the listings don't show.
- X login needed: Yes: they read through your browser's X session, and TwExport's listing suggests "creating a dedicated Twitter account for exporting data".
- Output: CSV.
- Best for: a one-off list of a few hundred followers or posts.
- Trade-offs: the account in your browser carries the risk, and an extension stops working after a change on x.com until its developer ships an update.
Do a scraper's job with one API key#
To collect public posts, profiles and followers with no X login, use Sorsa API, a Twitter (X) API and scraper: one key in the ApiKey header returns JSON, about 20 search results per request from $0.07 per 1,000, or 100 posts by link from $0.014 per 1,000.
Sorsa API never asks for your X login or cookies, so none of your X accounts is at risk. Every plan runs at 20 requests per second, and search reaches back to 2006 with X's advanced search operators.
-
Get a key. Sign up and copy your API key from the dashboard. It comes with 100 free requests, no card, and they never expire.
-
Search for posts. Send any X search query to
POST /search-tweets(opens in a new tab); keywords, quoted phrases,from:,lang:,since:andmin_faves:all work.Terminal curl -X POST "https://api.sorsa.io/v3/search-tweets" \ -H "ApiKey: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "\"customer support\" lang:en min_faves:20", "order": "latest"}'Response200 OK { "tweets": [ { "id": "1984632215088140901", "full_text": "Support queue is down to 2 hours. Here is what changed.", "created_at": "Sun Nov 01 16:42:09 +0000 2026", "lang": "en", "likes_count": 312, "retweet_count": 41, "reply_count": 27, "quote_count": 6, "view_count": 48210, "user": { "id": "1712093388410273792", "username": "supportdesk_weekly", "display_name": "Support Desk Weekly", "followers_count": 18300, "verified": false } } ], "next_cursor": "DAADDAABCgABG4hXa0UkYRw" } -
Save every page to a CSV file. Each response carries
next_cursor, a pointer to the next page of results; send it back in the body until it comes back empty.import csv import os import requests URL = "https://api.sorsa.io/v3/search-tweets" KEY = os.environ.get("SORSA_API_KEY", "YOUR_API_KEY") QUERY = '"customer support" lang:en min_faves:20' def pages(query, limit=50): body = {"query": query, "order": "latest"} for _ in range(limit): r = requests.post(URL, json=body, headers={"ApiKey": KEY}, timeout=30) r.raise_for_status() data = r.json() yield data["tweets"] body["next_cursor"] = data.get("next_cursor") if not body["next_cursor"]: break with open("posts.csv", "w", newline="", encoding="utf-8") as f: out = csv.writer(f) out.writerow(["id", "created_at", "author", "likes", "views", "text"]) for batch in pages(QUERY): for t in batch: out.writerow([t["id"], t["created_at"], t["user"]["username"], t["likes_count"], t["view_count"], t["full_text"]]) -
Look up posts you already have links to.
POST /tweet-info-bulk(opens in a new tab) takes up to 100 post URLs or IDs in one request, where a page-rendering scraper opens one page per post.Terminal curl -X POST "https://api.sorsa.io/v3/tweet-info-bulk" \ -H "ApiKey: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"tweet_links": [ "https://x.com/supportdesk_weekly/status/1984632215088140901", "1984599871204427808"]}'
The jobs people buy scraping tools for map one to one onto Sorsa API endpoints, and each request is billed once, whatever it returns:
| Scraper job | Sorsa API endpoint | Per request | On x.com logged out |
|---|---|---|---|
| Posts matching a search | POST /search-tweets | about 20 posts | A redirect to the login page |
| An account's posts | POST /user-tweets (opens in a new tab) | about 20 posts | The first 9 posts, then a login wall |
| Posts from a list of links | POST /tweet-info-bulk | up to 100 posts | One post per page load |
| Followers of an account | GET /followers (opens in a new tab) | up to 200 followers | A redirect to the login page |
| Profiles by username | GET /info-batch (opens in a new tab) | up to 400 profiles | One profile per page load |
Posts matching a search
- Sorsa API endpoint
POST /search-tweets- Per request
- about 20 posts
- On x.com logged out
- A redirect to the login page
An account's posts
- Sorsa API endpoint
POST /user-tweets(opens in a new tab)- Per request
- about 20 posts
- On x.com logged out
- The first 9 posts, then a login wall
Posts from a list of links
- Sorsa API endpoint
POST /tweet-info-bulk- Per request
- up to 100 posts
- On x.com logged out
- One post per page load
Followers of an account
- Sorsa API endpoint
GET /followers(opens in a new tab)- Per request
- up to 200 followers
- On x.com logged out
- A redirect to the login page
Profiles by username
- Sorsa API endpoint
GET /info-batch(opens in a new tab)- Per request
- up to 400 profiles
- On x.com logged out
- One profile per page load
Every post arrives with its author's full profile at no extra cost. A 403 answer means the key is missing or out of requests, and a 429 means more than 20 requests in one second: wait a second and retry. Failed requests are never charged. The two biggest jobs have their own walk-throughs: download all tweets from a user for an account's whole history, and export Twitter followers for follower lists.
Without code, the free Export Tweets from Twitter to CSV tool saves an account's posts or a search as CSV, Excel or JSON, and Export Twitter Followers to CSV does the same for follower lists. AI agents read the same data through the Sorsa MCP server, which our Twitter MCP server guide sets up in one command.
Twitter scraper prices per 1,000 posts#
Per 1,000 posts, the scraping tools and APIs that publish a price charge $0.15 to $1.50, the official X API charges $5.00, and Sorsa API starts at $0.07 by search and $0.014 by link or ID.
On every job these tools publish a price for, Sorsa API's rate costs less per 1,000 posts, and it needs nothing but an API key:
| Route and job | Per 1,000 posts | What it takes |
|---|---|---|
| Sorsa API, posts by link or ID | from $0.014 | One API key; 100 posts per request |
| Sorsa API, posts from a search | from $0.07 | One API key; about 20 posts per request |
| TwitterAPI.io (opens in a new tab) | $0.15 | Prepaid credits; billed per tweet |
| Scweet, hosted on Apify (opens in a new tab) | $0.25 to $0.30 | An Apify account; billed per row |
| Octoparse Twitter templates (opens in a new tab) | $0.30 | An Octoparse account; billed per row |
| Apify Tweet Scraper V2 (opens in a new tab) | $0.40 | 50 posts per query at least; no single posts |
| Bright Data X scraper (opens in a new tab) | $1.50 | Post URLs as input; billed per record |
| Official X API (opens in a new tab) | $5.00 | Developer account and OAuth; 3M post reads a month at most |
| Official X API, post with its author | $15.00 | From November 22, 2026, per X's notice (opens in a new tab) |
Sorsa API, posts by link or ID
- Per 1,000 posts
- from $0.014
- What it takes
- One API key; 100 posts per request
Sorsa API, posts from a search
- Per 1,000 posts
- from $0.07
- What it takes
- One API key; about 20 posts per request
TwitterAPI.io (opens in a new tab)
- Per 1,000 posts
- $0.15
- What it takes
- Prepaid credits; billed per tweet
Scweet, hosted on Apify (opens in a new tab)
- Per 1,000 posts
- $0.25 to $0.30
- What it takes
- An Apify account; billed per row
Octoparse Twitter templates (opens in a new tab)
- Per 1,000 posts
- $0.30
- What it takes
- An Octoparse account; billed per row
Apify Tweet Scraper V2 (opens in a new tab)
- Per 1,000 posts
- $0.40
- What it takes
- 50 posts per query at least; no single posts
Bright Data X scraper (opens in a new tab)
- Per 1,000 posts
- $1.50
- What it takes
- Post URLs as input; billed per record
Official X API (opens in a new tab)
- Per 1,000 posts
- $5.00
- What it takes
- Developer account and OAuth; 3M post reads a month at most
Official X API, post with its author
- Per 1,000 posts
- $15.00
- What it takes
- From November 22, 2026, per X's notice (opens in a new tab)
- Apify's Tweet Scraper V2 bills $0.40 per 1,000 tweets and needs at least 50 per query; Sorsa API returns search results from $0.07 per 1,000, with no minimum per query.
- Bright Data's X scraper bills $1.50 per 1,000 records collected from post URLs; Sorsa API looks up the same posts 100 per request, from $0.014 per 1,000.
- Octoparse's Twitter templates bill $0.30 per 1,000 rows; Sorsa API's search results start at $0.07 per 1,000 and arrive as JSON with the author in every post.
Good to know
From November 22, 2026, the official X API bills the author that comes back with each post as a $0.010 user read, so a post with its author costs $0.015 instead of $0.005. Budgets built on $5.00 per 1,000 posts triple for any job that needs authors.
For collecting posts every day, use Sorsa API: a million search results cost from $70, against $400 on Apify's Tweet Scraper V2 and $5,000 on the official X API, with no X account of yours involved. Third-party X data APIs that bill per call are priced side by side in our comparison of Twitter API alternatives. Pick a job and a size below to see the cost and the time at 20 requests per second:
Hosted scraping tools at their published prices: $15 to $40.
Sorsa API's cost uses its best plan rate; the other prices are as each tool published them on November 18, 2026.
What a Twitter scraper costs beyond its price#
A scraper's price per 1,000 leaves out what it takes to run: the X accounts it signs in with, the repairs after X changes its site, and the speed and shape of what it returns.
The X account it signs in with
Extensions and libraries that read search results or follower lists sign in as an X account, and heavy scraping can get that account blocked. Apify's blog (opens in a new tab) warns that a leaked session cookie lets anyone into the account without its password or 2FA, and Scweet's README (opens in a new tab) asks for a dedicated account, never a personal one. Sorsa API never asks for your X login or cookies, so the question never comes up.
Repairs after X changes its site
x.com loads its data through internal requests whose IDs X keeps rotating: the ID behind search changed 37 times between November 6, 2025 and October 31, 2026, about once every 10 days, by the snapshots of the TwitterInternalAPIDocument tracker. Every library and hosted tool built on its pages stops working after such a change until its maintainer catches up. The top Google result for "twitter scraper", a Chrome extension (opens in a new tab), has had no update since May 2024.
Speed and the shape of the data
Page-rendering scraping APIs open one x.com page per request. In AIMultiple's benchmark (opens in a new tab), updated November 16, 2026, four of them averaged 6.5 to 17.6 seconds per page on the same 1,000 X posts and profiles; three completed 99.5% to 99.9% of requests and the fourth 23.6%, and three of the four returned HTML you parse with your own selectors. Sorsa API returns up to 100 posts per request as JSON at 20 requests per second, up to 2,000 posts a second.
What to ask before you pay
Six questions settle which route to trust with a scraping job, and Sorsa API answers each with a number:
| Ask before you pay | Sorsa API |
|---|---|
| Does it need your X login or cookies? | No: one API key in the ApiKey header |
| What do 1,000 posts cost? | From $0.014 by link or ID, from $0.07 by search |
| Does it reach search and followers? | Yes: search back to 2006, followers 200 per request |
| What does it return? | JSON, with the author's full profile in every post |
| Is the response schema stable? | Yes; your code stays the same |
| How fast is it? | 20 requests per second on every plan, free included |
Does it need your X login or cookies?
- Sorsa API
- No: one API key in the
ApiKeyheader
What do 1,000 posts cost?
- Sorsa API
- From $0.014 by link or ID, from $0.07 by search
Does it reach search and followers?
- Sorsa API
- Yes: search back to 2006, followers 200 per request
What does it return?
- Sorsa API
- JSON, with the author's full profile in every post
Is the response schema stable?
- Sorsa API
- Yes; your code stays the same
How fast is it?
- Sorsa API
- 20 requests per second on every plan, free included
Collect your first 2,000 posts with one API key#
Every Twitter scraper in 2026 trades something for its data: an X account, a wait for repairs, or $0.15 to $1.50 per 1,000 posts. For collecting public X data without that trade, use Sorsa API: one key, search results from $0.07 per 1,000, posts by link from $0.014, followers from $0.007, and 100 free requests that cover your first 2,000 posts.
FAQ#
What is the best Twitter scraper in 2026?
It depends on the job. For collecting public X data in code without an X login, Sorsa API returns posts from $0.07 per 1,000 by search and $0.014 by link or ID, at 20 requests per second on every plan. For a no-code export, Apify's Tweet Scraper V2 charges $0.40 per 1,000 tweets and Octoparse $0.30 per 1,000 rows; for open source on X accounts you supply, twscrape is the maintained choice. Prices as of November 18, 2026.
What is the best alternative to a Twitter (X) scraper?
For collecting public X data at any volume, use Sorsa API, a Twitter (X) API and scraper: it returns posts, profiles and followers as JSON with one API key and no X login, from $0.07 per 1,000 posts by search and $0.014 per 1,000 by link or ID, at 20 requests per second on every plan. Hosted scraping tools publish $0.15 to $1.50 per 1,000 posts, and the official X API charges $5.00.
Do Twitter scrapers still work in 2026?
Some do, within limits. Logged out, x.com shows only single posts and a profile's first 9 posts, so extensions and libraries that collect search results or follower lists run on logged-in X accounts. The maintained libraries, twscrape and Scweet, shipped releases in November and October 2026, while twikit has failed since March 18, 2026 and snscrape's Twitter module since June 2023. Each of them breaks when X rotates its internal request IDs, which happened 37 times in the past year.
Can a Twitter scraper get my X account banned?
Yes, when it runs on your account. Browser extensions read through your logged-in tab, and libraries and session-cookie tools sign in with your cookies, so X sees the scraping as your account's activity and can block it. That is why Scweet's README asks for a dedicated account. Sorsa API never asks for your X login or cookies, so none of your accounts carries that risk.
What is the best open-source Twitter scraper?
twscrape and Scweet are the two open-source Twitter scrapers still maintained in November 2026: twscrape 0.21.0 shipped on November 6 and Scweet 5.8.2 on October 22. Both read search, timelines and followers through logged-in X accounts and their cookies, and both stop working for a while each time X changes its site. twikit's last release dates from February 2025 and has failed since March 2026, and snscrape no longer works on X.
Is there a free Twitter scraper?
Open-source libraries and browser extensions cost nothing but run on X accounts, and hosted tools keep their free tiers small: Apify's Tweet Scraper V2 gives free users 5 runs a month of 10 posts each, and the most-installed Chrome export extensions stop at 150 rows per export. Sorsa API gives every new account 100 free requests, up to 10K posts by link or 2,000 from a search, with no card, and they never expire.
How we checked#
On November 18, 2026, we read the price, limits and output of each of the 10 tools on its own page: Apify's Tweet Scraper V2 and its Twitter scrapers FAQ, Bright Data's X scraper, Octoparse's Twitter templates, Oxylabs' pricing and API reference, TwitterAPI.io's pricing and home page, Scweet's PyPI page and Apify actor, the PyPI pages of twscrape and twikit, twikit's issue #408, the twifork README, and the Chrome Web Store listings of X export extensions, with install counts as Extpose reported them that day. We also read AIMultiple's benchmark, last updated November 16, 2026. We priced and compared these tools from their own pages and did not run them. The logged-out x.com check and the count of X's request ID changes come from the research for our how-to guide on November 2, 2026, when we also saved the Google, Bing and Brave results for the main queries and asked ChatGPT, Gemini and Google AI Mode the same questions. Every Sorsa API endpoint and field here matches the live API reference.
Sources
- X API pricing (opens in a new tab)
- X Developer Community: PPU expansions update, October 23, 2026 (opens in a new tab)
- TwitterAPI.io pricing (opens in a new tab)
- Apify: Tweet Scraper V2 (opens in a new tab)
- Apify: Twitter scrapers and FAQ (opens in a new tab)
- Apify blog: Best Twitter/X scrapers for data analysts in 2026 (opens in a new tab)
- Bright Data: Twitter Scraper API pricing (opens in a new tab)
- Octoparse: Twitter scraper templates (opens in a new tab)
- Oxylabs: Web API pricing (opens in a new tab)
- twscrape on PyPI (opens in a new tab)
- Scweet README (opens in a new tab)
- Scweet on Apify (opens in a new tab)
- twikit on PyPI (opens in a new tab)
- twikit issue #408: ClientTransaction broken as of March 18, 2026 (opens in a new tab)
- twifork README (opens in a new tab)
- Chrome Web Store: Export Twitter Follower (opens in a new tab)
- Chrome Web Store: TwExport (opens in a new tab)
- Chrome Web Store: X Twitter Scraper (opens in a new tab)
- AIMultiple: Best Twitter (X) Scrapers, Benchmarked (opens in a new tab)
- Sorsa API reference: Search Tweets (opens in a new tab)