Search X / Twitter with one API call
Read X / Twitter — search tweets with engagement metrics — without building or maintaining a scraper. Maintained upstream with automatic failover. Same response shape as every other platform here, so one parser handles all of them. 5 credits a call.
The call
curl -H "x-api-key: $SS_KEY" \ "https://api.socialsearchapi.com/v1/x/search?query=llm+agents"
This call costs 5 credits once you are on credits. A new account gets 5 free calls on any platform — verify an email and this command runs as-is.
What comes back
A real response from this endpoint, captured on 2026-07-25 and trimmed to one item:
{
"success": true,
"platform": "x",
"data": {
"total": 20,
"items": [
{
"id": "2080887216629231629",
"platform": "x",
"type": "post",
"text": "@elonmusk @danrobinson Context + prompt injections combined into a portable protocol stack you can force feed to an A...",
"url": "https://x.com/LawtonAver58308/status/2080887216629231629",
"author": "LawtonAver58308",
"author_name": "Avery Lawton",
"created_at": "2026-07-25T05:25:48Z",
"metrics": {
"comments": 0,
"likes": 0,
"quotes": 0,
"reposts": 0,
"views": 14
},
"extra": {
"author_followers": 1303,
"created_at_raw": "Sat Jul 25 05:25:48 +0000 2026",
"lang": "en"
}
}
]
},
"credits_used": 5
}Items from X / Twitter carry: author, author_name, created_at, extra, id, metrics, platform, text, type, url.
Why not just scrape it yourself
X's official API is pay-per-use at roughly $0.005 per post read with the flat tiers closed to new signups, so a search-heavy workload gets expensive fast and reselling it is negative-margin. Scraping x.com directly means solving its request signing and staying logged in.
- Cost here: 5 credits a call, $0.015 at list.
- Last verified 2026-07-25: 2,530ms for this call.
- Coverage: Public tweets only. No protected accounts, no DMs, no deleted posts.
If you got here from an error
Get a free key — 5 calls, no card