Social Media · Twitter / X Scraper
Twitter / X User Tweets Scraper API
Pull an X account's timeline, page by page, with full text, media, and reply, repost, like and view counts on each post. No headless browsers, no captchas, proxies included.
// Twitter / X · User Tweets
curl -H "X-API-Key: hpx_your_key_here" \
"https://hproxy.com/api/v1/scrape/twitter/tweets?handle=nasa"
// → { "data": { … }, "records": 1, "costUsd": … }
TikTok
Facebook
YouTube
Instagram
LinkedIn
Reddit
Threads
Google
Pinterest
Twitch
Bluesky
Truth Social
Spotify
Snapchat
SoundCloud
Kick
Linktree
Komi
Pillar
Linkbio
Linkme
AmazonFrom Request to Clean JSON
You write one line. We do everything between the request and the data.
You send
One API call
GET the Twitter / X endpoint with your key. That's all your code does.
We handle
Proxies · captchas · parsing
Residential exit, anti-bot walls, JS rendering and extraction, all server-side, on us.
You get
Clean JSON
A structured object every time. No HTML, no scraping code, no maintenance.
The Twitter / X User Tweets endpoint is one API call: send an account handle with your HProxy key and get back a clean, structured JSON object. Pull an X account's timeline, page by page, with full text, media, and reply, repost, like and view counts on each post. HProxy runs the proxies, sessions, anti-bot handling and parsing server-side, so there is no headless browser to babysit and no parser to keep fixing when Twitter / X changes its markup. You only ever touch the JSON.
What the Twitter / X User Tweets API returns
text
Full post text with entities resolved.
stats
Replies, reposts, likes, bookmarks and views.
media[]
Attached images and video with direct URLs.
quoted / inReplyTo
The quote and reply chain around it.
Example response
{
"id": "1889...",
"text": "shipped it. took four days.",
"author": { "username": "@handle", "followerCount": 90421 },
"stats": { "replies": 84, "reposts": 312, "likes": 4120, "views": 291043 },
"media": [ { "type": "photo", "url": "https://.../img.jpg" } ],
"quoted": null
}Trimmed for brevity. Every call returns the full object with all fields listed here.
The Twitter / X user tweets endpoint
Full Twitter / X reference →/api/v1/scrape/twitter/tweetsParameters
handlestringrequiredAccount handle or @username.
trimbooleanoptionalReturn a slimmed-down payload (drops verbose fields).
Example request
curl "https://hproxy.com/api/v1/scrape/twitter/tweets?handle=nasa" \
-H "X-API-Key: hpx_your_key_here"POST with a JSON body works too. Failed calls, timeouts and rate-limited calls are never billed.
Scraping Twitter / X user tweets in three steps
Create a free account
Sign up and top up any amount. The balance pays for every HProxy product and never expires.
Grab your API key
One key from the dashboard authenticates every scraper, Twitter / X user tweets included.
Call the endpoint
Send the target to the Twitter / X User Tweets endpoint and read the JSON. That is the whole integration.
No captchas, ever
Anti-bot walls, JS rendering and rate limits are handled server-side. You call an API, that is the whole job.
Residential-backed
Every request exits through HProxy's own residential network, so it looks like a real user on a real device.
Pay per call
No subscription, no seat licenses. Calls are billed from your balance and the balance never expires.
Fresh on every call
Responses are scraped live at request time, no stale cache dressed up as data.
Failures are free
Automatic retries first; if an extraction still fails, the call is not charged.
Scales with you
From one call to millions: same endpoint, same price curve, volume discounts as you grow.
What people build with it
Archive posts before they are edited or deleted.
Track how a narrative spreads through quotes and replies.
Feed a monitoring tool with full post objects.
Twitter / X User Tweets pricing
$3.00
per 1,000 calls · 0.3¢ each
Pay per call, no subscription
Failed extractions are not charged
Proxies included in the price