Skip to content
Get 100 free requests

Twitter (X) Scraper API

Scrape tweets, profiles, followers and search results as clean JSON. No proxies, no cookies, no X account, and nothing to fix when X changes: we fix it on our side. Tweets from $0.014 per 1,000, up to 250x cheaper than the official X API.

Get 100 free requestsSee pricing

No credit card, and they never expire.

  • 6B+requests served
  • 2,500+developers
  • 100+companies
  • 99.9%uptime
cURL
curl -X POST https://api.sorsa.io/v3/search-tweets \
  -H "ApiKey: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "\"climate tech\" min_faves:100 lang:en", "order": "latest"}'
Response
{
  "tweets": [
    {
      "id": "1986034127730184704",
      "full_text": "Grid-scale storage passed 1 TWh worldwide this quarter.",
      "created_at": "2026-11-03T14:12:09Z",
      "likes_count": 412,
      "retweet_count": 96,
      "view_count": 58210,
      "user": { "username": "fieldnotes_climate_lab", "followers_count": 18240 }
    }
  ],
  "next_cursor": "DAACCgACGdyKq1x"
}

What you can scrape from Twitter (X)

Tweets and timelines

Any public account’s posts, replies and retweets, back to its very first tweet. No 3,200-tweet cap.

Search, back to 2006

Every X Advanced Search operator: keywords, accounts, dates, engagement, language, media. Latest or top results.

Profiles

Full public profiles, 100 per request, by username or user ID: bio, counts, location, join date, verification.

Followers and following

Up to 200 profiles per request, verified followers included. A 100,000-follower account takes about 500 requests.

Engagement

Replies, quote tweets, retweeters and mentions of any public post or account.

Lists, Communities, Spaces, trends and X Articles

Tweets and members of public Lists and Communities, Spaces, trends by location and full X Articles.

Checks

Follows, retweets, quotes, comments, community membership and shadowbans, one call each.

Scrape Twitter in one request

One HTTPS request with your API key returns clean JSON. Page through results with next_cursor, 20 requests per second on every plan.

cURL
curl -X POST https://api.sorsa.io/v3/search-tweets \
  -H "ApiKey: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "\"climate tech\" min_faves:100 lang:en", "order": "latest"}'
Python
import requests

API_KEY = "YOUR_API_KEY"
tweets, cursor = [], None

while len(tweets) < 1000:
    body = {"query": "\"climate tech\" min_faves:100 lang:en", "order": "latest"}
    if cursor:
        body["next_cursor"] = cursor
    r = requests.post("https://api.sorsa.io/v3/search-tweets",
                      headers={"ApiKey": API_KEY}, json=body, timeout=30)
    r.raise_for_status()
    data = r.json()
    tweets += data["tweets"]
    cursor = data.get("next_cursor")
    if not cursor:
        break

print(len(tweets), "tweets scraped")

Twitter scraper API vs DIY scrapers and scraping platforms

Same public data. No proxies to rent, no accounts to lose, no scripts to fix.

Sorsa APIDIY scrapers (Playwright, twscrape)Scraping platformsOfficial X API
Price per 1,000 tweetsfrom $0.014free code, plus proxies and X accounts$0.40 (Apify Tweet Scraper V2) to $1.50 (Bright Data)$5.00
Proxiesnoneresidential proxies to rentbuilt into the pricenone
X accountneverrequired, at risk of a lockdepends on the tooldeveloper account and OAuth
When X changes somethingwe fix it on our sidebreaks until you fix itwaits for the vendor’s fixstable
Speed20 requests per second on every planthrottled and blocked by Xper runper-endpoint 15-minute windows
Setup3 minutesdayshoursdeveloper account, app and OAuth

Why a scraper API beats a DIY Twitter scraper

X changed the query ID of its search operation 37 times in 12 months, about once every 10 days. A default headless browser on a server gets HTTP 403 on its first request, and X locks accounts that look automated. A home-made Twitter scraper needs residential proxies, a pool of X accounts and someone on call to fix it after every change.

Sorsa API runs all of that for you. You send one HTTPS request with your API key and get the same JSON schema every time: when X changes something, we fix it on our side. In production since 2022, with 6B+ requests served for 2,500+ developers and 100+ companies.

From $0.014 per 1,000 tweets

Flat per-request plans from 10,000 to 10 million requests a month. One request returns up to 100 tweets, 100 profiles or 200 followers, so you pay per request, not per result. Every new account starts with 100 free requests: up to 10,000 tweets or 20,000 profiles, no card, no expiry.

Get 100 free requestsSee pricing

Twitter scraper API questions, answered.

Yes, for public data. In hiQ Labs v. LinkedIn, the US Ninth Circuit held that scraping public pages is likely not access “without authorization” under the Computer Fraud and Abuse Act, and in May 2024 a federal court dismissed X’s lawsuit against Bright Data over scraping public posts. Sorsa API returns only public X data, the same data any browser or search engine sees without logging in, and you never log in to X, so no account of yours is at risk.

No. Sorsa API never asks for your X login, cookies or session tokens, and nothing runs on an X account of yours, so there is nothing for X to ban. Bans hit browser extensions and DIY scrapers, because they run on your logged-in account.

No. Proxies, browsers, tokens and account pools are our job. You send one HTTPS request with your API key and get clean JSON back.

Yes. Every new account gets 100 free requests: up to 10,000 tweets or 20,000 profiles, no credit card, and they never expire. For one-off jobs, the free Tweet Scraper and Twitter Followers Scraper export to CSV or Excel with no code.

As many as you need. Search goes back to 2006, timelines have no 3,200-tweet cap, and plans run from 10,000 to 10 million requests a month. At 20 requests per second, that is up to 2,000 tweets a second.

Yes. GET /followers returns up to 200 followers per request with full profiles, so a 100,000-follower account takes about 500 requests. Following lists and verified followers work the same way.

Yes. POST /search-tweets accepts every X Advanced Search operator, including since:, until:, from:, min_faves: and lang:, and returns the latest or the top results back to 2006.

The official X API bills $5.00 per 1,000 posts and $10.00 per 1,000 profiles, caps pay-per-use at 3 million posts a month and asks for a developer account and OAuth. Sorsa API is up to 250x cheaper, needs one API key and no approval, and runs 20 requests per second on every plan.

Start scraping Twitter in 3 minutes.

Sign up, grab your API key, paste a curl command. Your first 100 requests are free: no card, no expiry.

Get 100 free requests