X (Twitter) User Tweets Scraper
Pricing
from $0.05 / 1,000 tweets
X (Twitter) User Tweets Scraper
Scrape recent tweets from any public X/Twitter user by handle. No login or API key. Fast, structured JSON.
Pricing
from $0.05 / 1,000 tweets
Rating
0.0
(0)
Developer
Gurify Software
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
X (Twitter) User Tweets Scraper π¦
Scrape recent tweets from any public X/Twitter user by username β no login, no API key, no developer account. Give it a list of handles, get clean structured tweets (text, metrics, media, links) as JSON. Built for reliability: it fetches straight from x.com and self-heals when X changes its internals.
π΅ $0.05 per 1,000 tweets β one of the cheapest X scrapers on Apify (most cost $0.15β$0.40).
β¨ What you get
- Just usernames in β tweets out.
["elonmusk", "nasa"]β their latest tweets. - Rich structured data per tweet β text, created date, like/retweet/reply/quote/bookmark/view counts, language, media (images + video URLs), hashtags, mentions, links, and flags for retweet/reply/quote.
- Pagination β pull up to ~3,200 tweets per user (X's public timeline cap).
- No X API needed β no $200/mo X API tier, no app registration, no OAuth.
- Reliable β auto-harvests X's rotating GraphQL query-ids on every run, so it keeps working when other scrapers break. Residential proxies + Chrome TLS fingerprinting get clean responses.
π₯ Input
| Field | Type | Description |
|---|---|---|
handles | array (required) | Usernames with or without @, or full profile URLs. e.g. ["elonmusk", "@nasa", "https://x.com/spacex"] |
tweetsPerHandle | integer | Max tweets per user (default 20, up to 3200) |
includeReplies | boolean | Include the user's replies (default false) |
includeRetweets | boolean | Include retweets, shown as the original author (default true) |
proxyConfiguration | object | Apify Proxy (required). Datacenter (default) is cheapest and works; switch to Residential for very high-volume runs |
{"handles": ["elonmusk", "nasa"],"tweetsPerHandle": 50,"includeReplies": false,"includeRetweets": true,"proxyConfiguration": { "useApifyProxy": true }}
π€ Output
One dataset item per tweet:
{"id": "2069445014787129590","url": "https://x.com/elonmusk/status/2069445014787129590","text": "β¦","createdAt": "2026-06-23T15:38:34+00:00","authorUserName": "elonmusk","authorName": "Elon Musk","authorId": "44196397","replyCount": 12043, "retweetCount": 8021, "likeCount": 91244,"quoteCount": 410, "bookmarkCount": 1900, "viewCount": 12840322,"lang": "en","isRetweet": false, "isReply": false, "isQuote": false,"hashtags": [], "mentions": [], "links": [],"media": [{ "type": "photo", "imageUrl": "https://pbs.twimg.com/β¦" }],"queryHandle": "elonmusk"}
Export to JSON, CSV, Excel, or pull via the Apify API.
π΅ Pricing β $0.05 / 1,000 tweets
Just $0.05 per 1,000 tweets (pay-per-result) β among the cheapest X scrapers on Apify (most charge $0.15β$0.40 per 1,000). No monthly fee, no commitment, no API key; you only pay for tweets you actually get.
βοΈ How it works / reliability
It calls x.com's own guest GraphQL endpoints (the same ones the website uses), through Apify Proxy with a real Chrome TLS fingerprint, and auto-discovers X's GraphQL query-ids from x.com's JavaScript (cached ~6h) β so when X rotates them (which breaks most scrapers), this one adapts automatically.
β οΈ Limitations
- Public accounts only β protected/suspended accounts return nothing.
- User timelines only (v1) β keyword/hashtag search and full conversation threads aren't included yet (X gates search behind login).
- Counts/fields reflect what X exposes publicly at fetch time.
β FAQ
Do I need an X account or API key? No. Which proxy? Apify Proxy is required. Datacenter (the default) works and is cheapest; pick Residential only for very high-volume runs or if datacenter ever gets blocked. Will it break when X changes their API? It auto-harvests query-ids (cached ~6h) to stay ahead of rotations; if X makes a deeper change, updates ship quickly.
βοΈ Legal
Scrapes only publicly available data. You are responsible for using the output in line with X's terms and applicable laws (e.g. GDPR/CCPA) β don't use it to harass, profile, or for prohibited purposes.