Sorsa API

Sorsa API is a read-only REST API for public X (Twitter) data. It covers 41 endpoints across user profiles, posts, advanced search, followers and following, Lists, X Articles, Spaces, trends, and action verification, and returns clean JSON. On your side, a single Sorsa API key is the whole setup, with no X developer-account application. Pricing is flat per request, from $0.02 per 1,000 tweets, and every new account starts with 100 free requests. Sorsa has run in production since 2022, first as TweetScout API.

No. The only credential you need is a Sorsa API key, issued instantly when you sign up. You do not file an X developer application, complete an OAuth flow, or wait in an approval queue, and you never share your own X login or cookies with Sorsa. Create an account, copy the key from the dashboard, pass it in the ApiKey header, and your first request works within minutes.

Sorsa API returns public X data: user profiles (one at a time or 100 per batch), followers and following lists (200 per page), posts by ID (100 per batch), full user timelines, replies, quote posts, retweeters, keyword and mention search with the full advanced-search operator set, Lists, X Articles, Spaces, trends by location, account About data such as based-in country, and verification checks that confirm whether a user followed, retweeted, quoted, or replied. Out of scope: protected accounts, DMs, who liked a post, a user’s likes or bookmarks, deleted posts, and any write action such as posting, liking, following, or messaging. Sorsa is read-only by design. The full endpoint list is in the API reference.

Sorsa bills per request; the official X API bills per resource. On X, every post, profile, and follower in a response is a separate charge, about $5.00 per 1,000 post reads plus $10.00 for their authors’ profiles, and reads are capped at 3 million posts a month. On Sorsa, one request returns up to 100 tweets or 200 profiles with author data included, so 1,000 tweets cost from $0.02, up to 50x cheaper on read-heavy work. On your side, a single Sorsa API key replaces OAuth and a developer application. The trade-off is that Sorsa is read-only: posting, DMs, and other write actions stay with the official API. For a step-by-step switch, see the migration guide.

Three ways. Pricing is flat per request rather than metered per item, and batch endpoints return up to 100 tweets or 200 profiles in one request, which is how Sorsa reaches $0.02 per 1,000 tweets where per-item APIs typically charge several times more. Coverage includes what many alternatives skip: follow, retweet, quote, and reply verification, X Articles, Spaces, and account About data such as based-in country. And Sorsa is a managed service: the response schema stays stable, and when X ships changes to its platform the fix happens on our side, not in your codebase.

Yes. Every request is served live when you call it, so follower counts, engagement metrics, and search results reflect X at that moment rather than a cached copy. Median response time is about 300 ms. Sorsa does not provide a streaming firehose or webhooks; real-time monitoring works by polling at up to 20 requests per second, which every plan includes. The one exception is the shadowban check, whose result is cached for one hour per handle.

To an account’s first post. User timelines paginate through the entire posting history with no 3,200-tweet cap, and search accepts since: and until: operators back to 2006, so you can pull old posts for any keyword, hashtag, or account. Engagement counts come back as they stand at request time. Follower and following lists reflect the current graph; Sorsa does not store historical snapshots of who followed whom. For methods and code, see the guide to historical X data.

20 requests per second on every plan, Starter through Enterprise, with all endpoints included and no throttling on lower tiers. Since one request can return up to 100 tweets or 200 profiles, that is up to 2,000 tweets or 4,000 profiles per second before pagination. Plans differ only in monthly volume: 10,000, 100,000, 250,000, or 500,000 requests. High-volume plans (1M to 10M requests a month) and custom plans can get a higher dedicated rate limit; contact sales to set one up.

Nothing on your side. When X ships changes to its platform, the Sorsa team handles the update, the response schema stays the same, and your integration keeps running without code changes. That is the practical difference between a maintained service and a DIY script or open-source library that you have to fix yourself after every X update. Sorsa has run in production since 2022, and the public status page shows live uptime and latency.

No. Sorsa is an independent service and is not affiliated with, endorsed by, or sponsored by X Corp; X and the X logo are trademarks of X Corp. You access public X data through Sorsa’s own API, dashboard, and Terms of Service, and you remain responsible for using, storing, and sharing that data in line with the laws that apply to you and your project, including any privacy rules that cover the people whose posts you process. Nothing on this page is legal advice.