SocialData and TwittrAPI both serve X data through a REST API with a key from a dashboard. SocialData charges per tweet or profile returned. We charge per call. SocialData also reshapes the data into flat objects, while we pass X's JSON through.
We run TwittrAPI. SocialData details below come from its homepage and docs, checked on 10 October 2026; each number links to its source.
At a glance (as of October 2026)
X-API-KEY headerAuthorization: Bearer headercursor in; bottom cursor inside X's JSONcursor in; next_cursor outfull_text, favorite_count, screen_name)Price: per call vs per item
Profile lookups. SocialData charges $0.0002 per tweet or profileas of Oct 2026, one at a time or in batches. On TwittrAPI one profile lookup is one call, and GET /user/users/by/ids returns up to 100 profiles in one call. 1,000 profiles cost $0.065 to $0.09 one by one, or $0.00065 to $0.0009 in batches of 100.
Search and timelines. SocialData returns about 20 tweets per pageas of Oct 2026, which is about $0.004 per page of 20 tweetsas of Oct 2026. Our count defaults to 20, and X decides how many items come back. If a page holds 20 tweets, 1,000 tweets cost $0.20 per 1,000 tweets or profilesas of Oct 2026 on SocialData and $0.00325 to $0.0045 on TwittrAPI. That is an estimate; measure with your queries.
Empty results. SocialData charges only successful requests and bills search and timeline endpoints per item, so an empty page costs nothing there. We bill a call that succeeds, even if X returns an empty page. If your workload polls for new tweets that are often not there, that difference matters and can favour SocialData.
Where SocialData is the better fit
- Simple JSON. Flat objects you can use without writing a parser.
- Failed requests are not charged, and per-item billing means empty pages cost nothing, which suits polling.
- Endpoints we do not have: Spaces, threads, mentions, highlights, affiliates, similar profiles, extended bio, and checks such as "did this user retweet this tweet".
- Monitoring and webhooks, and an MCP server.
- A refund within 14 days if the deposit is unusedas of Oct 2026, and higher limits on request at no cost.
Where TwittrAPI is the better fit
- Lookups and batch lookups, especially up to 100 profiles per call.
- Pages of results, when each call returns many items.
- Trends by location, which SocialData's docs index does not list.
- Per-second throughput: 30 requests per second by default, against 120 requests per minute per useras of Oct 2026.
- A free start without contacting support: $0.10 test credit at sign-up.
- Every field X sends, because we do not reshape the JSON.
Endpoints side by side
GET /user/users/by/ids (up to 100)POST /twitter/users-by-ids (up to 100 IDs per callas of Oct 2026)GET /twitter/space/{space_id}The full mapping is in the migration guide. Our endpoint reference is in the docs.
How to decide
If you mostly look up profiles or tweets, or page through large timelines, run a sample on TwittrAPI with the $0.10 credit from /start and compare. If you depend on flat JSON, Spaces, monitoring, or you poll endpoints that are usually empty, SocialData may cost you less engineering time, which is worth more than a few cents per thousand.
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 SocialData?
On published prices, yes for lookups: 1,000 profile lookups cost $0.20 per 1,000 tweets or profilesas of Oct 2026 on SocialData and $0.065 to $0.09 on TwittrAPI, or less when you fetch up to 100 profiles per call. For search and timelines SocialData charges per tweet and we charge per page, so measure with your own queries.
Does SocialData have a free tier?
Its homepage says no free planas of Oct 2026, and its pricing docs allow up to 3 requests per minute without chargeas of Oct 2026. TwittrAPI gives $0.10 of test credit for 14 days.
Which one has the simpler JSON?
SocialData. It returns flat snake_case objects with fields like full_text and favorite_count. TwittrAPI passes X's own JSON through, which needs a parser.
What are the rate limits?
SocialData documents 120 requests per minute per useras of Oct 2026, raised on request. TwittrAPI allows 30 requests per second per key after the first top-up, with higher tiers you can book.