Twitter Profile Scraper
An X (Twitter) profile's tweets as typed JSON, a page at a time: text, time, likes, retweets, replies, views, media and an author object with bio, followers and join date. 1 credit per call. No X login.
Free API key · 1 credit per page of tweets · failed calls free
// GET /api/v2/twitter-tweets/?usernames=elonmusk · sample from the catalog { "success": true, "data": { "usernames": "BillGates", "user_id": "50393960", "screen_name": "BillGates", "page": 1, "page_size": 20, "tweets": [ { "id": "1948167071684231344", "tweet_id": "1948167071684231344", "url": "https://x.com/BillGates/status/1948167071684231344", "verified": true, "username": "@BillGates", "fullname": "Bill Gates", "timestamp": "Wed Jul 23 23:43:19 +0000 2025", "text": "Learning how many kids were dying from diarrhea back in 1997 ... https://t.co/NYitqiRY38", "links": [ "https://gatesnot.es/46lTfBz" ], "isPinned": false, "isQuote": false, "isRetweet": false, "isReply": false } ], "next_cursor": "eyJoIjoiLi4uIiwiaW4iOiJCaWxsR2F0ZXMiLCJsdCI6IjE5MjYwNDY2MzQ0NDc1NTg1NjYiLCJwIjoyLCJyIjp0cnVlLCJzbiI6IkJpbGxHYXRlcyIsInUiOiI1MDM5Mzk2MCIsInVpIjp0cnVlfQ" } }
| field | value | type | Has a value✓ |
|---|
Scrapier's Twitter Profile Scraper returns the tweets of an X profile as JSON, about 20 per page: text, timestamp, likes, retweets, replies, views and a user object with the author's bio and follower count. It costs 1 credit per successful call. No X login.
Twitter Profile Scraper extracts the tweets of an X profile from a handle, a numeric user ID or a profile URL. Each tweet comes with its text, time, links, engagement counts, language, media and flags for pinned posts, replies, quotes and retweets. With include_user_info on, every tweet also carries the author's bio, location, website, join date and follower counts. Every response is structured JSON, ready to pass directly to an LLM, index into a vector store or feed an influencer-tracking pipeline. It is one of 6 X (Twitter) endpoints on the same API key used by 12,000+ developers. Follow next_cursor for older tweets.
What data can I extract with Twitter Profile Scraper?
Using this Twitter Profile Scraper, you can extract the following data from public X (Twitter) pages of tweets:
Want the exact field names? See the example output.
Try Twitter Profile Scraper Live
Press Run to see the catalog sample. Add your API key and it runs a real call to the Scrapier API from your browser. The key is sent only to proxy.scrapier.io and never stored.
+ Run live with your API key
How to use Twitter Profile Scraper
Hand it to your AI assistant, or run it yourself in five steps.
Copy to your AI assistant
Paste this into ChatGPT, Claude or Cursor and it knows how to call the scraper.
Use the Scrapier Twitter Profile Scraper to get public X (Twitter) pages of tweets. Endpoint: GET https://proxy.scrapier.io/api/v2/twitter-tweets/?usernames={usernames} with header "X-API-Key: YOUR_API_KEY" and a 210-second timeout. Send one value per call in usernames; for a list, make one call per value, at most 3 in parallel. It returns JSON under data.tweets: id, tweet_id, url, verified, username, fullname, timestamp, text, links, isPinned, isQuote, isRetweet. Each successful call costs 1 credit; failed calls are free. If you support MCP, run: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY" and call run_scrape with endpoint "twitter-tweets" (find it with search_endpoints).Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads X (Twitter) pages of tweets on its own: no glue code, no scraping logic in your prompts.
Run it yourself
- Get your free Scrapier API keySign up at app.scrapier.io; the free tier lets you try it first.
- Open Twitter Profile Scraper in the catalogIt lives under Scrapers / X (Twitter).
- Enter the profilePut a handle such as
BillGates, a numeric user ID or a profile URL inusernames. Setwith_repliesandinclude_user_infototrueorfalseas you need. - Send your API requestOne GET with your key in the
X-API-Keyheader, or onerun_scrapecall from your agent. Set a 210-second client timeout. - Save your resultsEach page comes back as JSON in
data.tweets: store it as is, or flatten it to CSV. Passdata.next_cursorback ascursorto get the next page until it is null.
How to scale to bulk X (Twitter) pages of tweets
usernames takes one value per call, so for a list you loop: one request per profile. Within a profile, pass back data.next_cursor to page through its tweets. Run up to 3 requests in parallel per API key; above that the API answers 429 with a Retry-After header, and throttled calls cost nothing. Each call is 1 credit and failed calls are free, so 1,000 calls cost 1,000 credits, inside the Hobby plan's 15,000.
Features
Twitter Profile Scraper turns an X timeline into clean rows. It suits influencer research, brand monitoring, content audits and any workflow that needs a profile's tweets with engagement and author context, without managing X sessions or API credentials.
- Tweets
text,urlandtweet_idfor every tweet - Engagement
likes,retweets,replies,quotes,bookmarks,views - Flags
isPinned,isReply,isQuoteandisRetweet - Replies
with_repliesincludes or leaves out replies - Author info
include_user_infoadds theuserobject - Paging
next_cursorwalks the timeline page by page
Proxies, retries and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per page of tweets and 0 credits for a failed call.
Use cases
- Influencer researcher pulls a creator's recent tweets with
likes,retweetsandviewsto see how consistently the account earns engagement. - Brand monitor polls a list of executive and competitor accounts each morning and sends new tweets with their
urlto a team channel. - Content strategist exports a profile's tweets to a sheet, sorts by
viewsand studies which topics and formats travelled. - Analyst lists tweets with
include_user_infoon to log follower counts next to every post for a time series. - AI engineer gives an agent a tool that fetches a profile's tweets, then asks an LLM to summarise the themes.
Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.
Why choose this Scraper API?
With include_user_info on, each tweet carries a user object with bio, location, website, join date and follower counts, so one call shows what was said and by whom.
with_replies lets you keep a clean feed of original tweets or include replies, and the choice is locked into the cursor.
The same key and response envelope cover posts, profile tweets and video transcripts, so a tweet URL from here feeds the next call without new code.
Input
The scraper takes one profile per call in usernames: an X handle, a numeric user ID or a profile URL. with_replies and include_user_info are optional and locked in the cursor once you start paging. Keyword and hashtag search is login-only on X and is not supported. Send parameters in the query string (GET) or as a JSON body (POST).
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
usernames | string | Yes | — | An X handle, numeric user ID or profile URL. One per call. Required on the first call, ignored when cursor is set. Aliases: username, user, users, profile |
cursor | string | No | — | Pass back data.next_cursor from the previous response to get the next page; null means the last page |
with_replies | boolean | No | true | true (default) includes replies, false leaves them out. Locked in the cursor |
include_user_info | boolean | No | true | true (default) adds the per-tweet user object. Locked in the cursor |
use_proxy | boolean | No | true | Route through Scrapier's rotating residential proxy pool, since X rate-limits anonymous calls per IP. Leave as is |
raw_data | boolean | No | false | Return X's raw upstream payload under raw_responses instead of the formatted items |
One profile per call: to scan ten profiles, make ten calls and page each with cursor. Booleans are the strings true or false.
Example input
{
"usernames": "elonmusk",
"with_replies": "true",
"include_user_info": "true",
"use_proxy": "true",
"raw_data": "false"
}Error codes
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Page of tweets data returned in data.tweets | Yes | — |
| 400 | Bad or missing input | No | Check usernames: one value per call |
| 401 | X-API-Key header missing | No | Add the header |
| 402 | Out of credits (body has balance) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait Retry-After seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry with backoff; set a 210 s client timeout |
From the error reference. Any non-2xx response costs 0 credits.
Output
Typed JSON with the same schema on every call. One call returns a page of tweets under tweets, each with 25 fields, inside the standard data envelope. data also carries the resolved user_id and screen_name, the page, page_size and next_cursor. Field names stay the same on every call. Set raw_data to true if you want X's raw payload instead.
Example output
{
"success": true,
"data": {
"usernames": "BillGates",
"user_id": "50393960",
"screen_name": "BillGates",
"page": 1,
"page_size": 20,
"tweets": [
{
"id": "1948167071684231344",
"tweet_id": "1948167071684231344",
"url": "https://x.com/BillGates/status/1948167071684231344",
"verified": true,
"username": "@BillGates",
"fullname": "Bill Gates",
"timestamp": "Wed Jul 23 23:43:19 +0000 2025",
"text": "Learning how many kids were dying from diarrhea back in 1997 ... https://t.co/NYitqiRY38",
"links": [
"https://gatesnot.es/46lTfBz"
],
"isPinned": false,
"isQuote": false,
"isRetweet": false,
"isReply": false,
"likes": 5219,
"replies": 0,
"retweets": 1816,
"quotes": 598,
"bookmarks": 334,
"views": 2828080,
"lang": "en",
"user": {
"avatar": "https://pbs.twimg.com/profile_images/1879013694367252480/Gxa-Pspq_normal.jpg",
"username": "BillGates",
"userFullName": "Bill Gates",
"description": "Sharing things I'm learning through my foundation work and other interests.",
"location": "Seattle, WA",
"website": "https://gatesnot.es/tgn",
"joinDate": "Wed Jun 24 18:44:10 +0000 2009",
"verified": true,
"totalLikes": 542,
"totalTweets": 4521,
"totalFollowing": 571,
"totalFollowers": 65231300,
"url": "https://t.co/TiXXwOGE95",
"userId": "50393960",
"totalMediaCount": 1530
},
"media": [],
"tweetUserId": "50393960",
"input_username": "BillGates",
"scraped_at": "2026-10-03T03:35:53.722Z"
}
],
"next_cursor": "eyJoIjoiLi4uIiwiaW4iOiJCaWxsR2F0ZXMiLCJsdCI6IjE5MjYwNDY2MzQ0NDc1NTg1NjYiLCJwIjoyLCJyIjp0cnVlLCJzbiI6IkJpbGxHYXRlcyIsInUiOiI1MDM5Mzk2MCIsInVpIjp0cnVlfQ"
}
}The catalog's sample response for usernames=elonmusk, labelled as a sample: live calls return the account's current values.
Tweet
| Field | Type | Example | Description |
|---|---|---|---|
tweets.id | string | "1948167071684231344" | Tweet ID |
tweets.tweet_id | string | "1948167071684231344" | Tweet ID (same value as id) |
tweets.url | string | "https://x.com/BillGates/status/194816707168…" | URL of the tweet |
tweets.text | string | "Learning how many kids were dying from diar…" | Text of the tweet |
tweets.timestamp | string | "Wed Jul 23 23:43:19 +0000 2025" | When the tweet was posted, as X formats it |
tweets.lang | string | "en" | Language code of the tweet |
tweets.links | array | 1 items | Links found in the tweet |
tweets.media | array | [] | Media attached to the tweet |
Engagement
| Field | Type | Example | Description |
|---|---|---|---|
tweets.likes | integer | 5219 | Number of likes |
tweets.replies | integer | 0 | Number of replies |
tweets.retweets | integer | 1816 | Number of retweets |
tweets.quotes | integer | 598 | Number of quote tweets |
tweets.bookmarks | integer | 334 | Number of bookmarks |
tweets.views | integer | 2828080 | View count |
Type flags
| Field | Type | Example | Description |
|---|---|---|---|
tweets.isPinned | boolean | false | true if the tweet is pinned |
tweets.isQuote | boolean | false | true if the tweet quotes another |
tweets.isRetweet | boolean | false | true if the tweet is a retweet |
tweets.isReply | boolean | false | true if the tweet is a reply |
Author
| Field | Type | Example | Description |
|---|---|---|---|
tweets.username | string | "@BillGates" | Handle with @ |
tweets.fullname | string | "Bill Gates" | Display name of the author |
tweets.verified | boolean | true | Whether the author is verified |
tweets.tweetUserId | string | "50393960" | Numeric user ID of the author |
tweets.user | object | {…} | Author object: avatar, username, userFullName, description, location, website, joinDate, verified, totalLikes, totalTweets, totalFollowing, totalFollowers, url, userId, totalMediaCount |
Input and timestamp
| Field | Type | Example | Description |
|---|---|---|---|
tweets.input_username | string | "BillGates" | The usernames value you sent |
tweets.scraped_at | string | "2026-10-03T03:35:53.722Z" | When Scrapier read the page (ISO 8601, UTC) |
Response envelope and paging
| Field | Type | Example | Description |
|---|---|---|---|
success | boolean | true | true on every 200 response |
data.usernames | string | "BillGates" | Your profile input, echoed back |
data.user_id | string | "50393960" | The resolved numeric user ID |
data.screen_name | string | "BillGates" | The resolved handle |
data.page | integer | 1 | Page number of this response |
data.page_size | integer | 20 | Tweets per page (20 in the catalog sample) |
data.next_cursor | string | "eyJoIjoiLi4uIiwiaW4iOiJCaWxsR2F0ZXMiLCJsdCI…" | Pass back as cursor for the next page; null on the last page |
How does it work?
Scrapier sends each request through its residential proxy pool (use_proxy, on by default), so you never manage IPs or proxy accounts.
Retries and parsing of X's responses happen on Scrapier's side. You send one HTTP request and get typed JSON back.
Only publicly visible data is returned: what any visitor sees without signing in. No X account, cookie or developer credential is used for this endpoint.
The schema is stable. When X changes, Scrapier updates the scraper and the field names stay the same.
How do you integrate Twitter Profile Scraper into your stack?
It works with what you already use: any HTTP client, AI agents over MCP, and no-code automation tools. Code samples for cURL, Python and Node.js are on the API tab.
MCP integration for AI agents
This registers the Scrapier MCP server, whose tools reach every Scrapier scraper, including twitter-tweets: the agent finds it with search_endpoints and calls it with run_scrape. Works with Claude Code, Cursor and Windsurf. MCP calls are billed like REST: 1 credit per successful call. Full MCP setup →
No-code tools (n8n, Make, LangChain)
Use the HTTP Request node with your Scrapier API key in an X-API-Key header and point it at /api/v2/twitter-tweets/ with the input as a query parameter. Map data into the next node.
Add an HTTP "Make a request" module with the same header and URL, and parse the response as JSON. Map the fields you need straight into Sheets, Airtable or your CRM.
Wrap the endpoint in a requests-based tool, or load the Scrapier MCP server through LangChain's MCP adapters so the agent finds twitter-tweets with search_endpoints itself.
Pricing and Rate Limits
One X (Twitter) page of tweets costs 1 credit, so 1,000 pages of tweets cost 1,000 credits: $1.58 on the Pro plan. Failed and empty calls are not billed. Run up to 3 requests in parallel per key; above that the API answers 429 with a Retry-After header.
| Plan | Monthly price | Credits | Pages of tweets included | Per 1,000 pages of tweets |
|---|---|---|---|---|
| Hobby | $29 | 15,000 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | 250,000 | $1.20 |
| Enterprise | Custom volume and terms | |||
Prices from the live billing page. See all plans and limits.
Call cost and timing
How we measure this
Credit cost, pagination and the sample come from the live catalog (GET /api/v2/endpoints, /twitter-tweets/, checked 9 Nov 2026). Concurrency and timeout guidance come from the rate limits page of the docs. Scrapier does not publish latency or success-rate figures for this endpoint, so none are shown here.
Twitter Profile Scraper vs the Official X (Twitter) API
| Feature | Scrapier page of tweets scraper | Official X (Twitter) API |
|---|---|---|
| Access needed | One Scrapier API key | A developer account, app credentials and a plan with access limits |
| Which tweets | Any public profile's tweets, replies on or off | Depends on the endpoints and access level of your plan |
| Fields returned | 25 fields per tweet, including text, engagement and author | Depends on the fields and expansions you request |
| Rate limits | Up to 3 parallel requests per key; 429 with Retry-After | Limits set per endpoint and plan |
| Setup | Sign up, copy a key, send a request | Apply for access, create an app, manage tokens |
| Cost | 1 credit per page, from $1.20 per 1,000 pages | Set by the plan you choose |
The official X API is the better choice when you post or act on behalf of a user, or need data that only the account owner can see.
Is it legal to scrape X (Twitter) data?
Scraping publicly available X (Twitter) data is generally lawful in many countries, but the answer depends on what you collect, where you are and how you use it. In the US, hiQ Labs v. LinkedIn is the case most often cited on public-data scraping. Scrapier returns only public tweets and profile details any visitor can see without logging in. Under GDPR and similar laws, collecting public data can be permissible, but how you store and use personal data, such as names, handles or posts, must still comply with local data-protection rules, and X's terms apply. Consult legal counsel if your use case involves bulk storage of personal data. This is not legal advice; see our Terms of Use.
Frequently asked questions
What fields does Twitter Profile Scraper return?
Each tweet has id, url, text, timestamp, lang, likes, replies, retweets, quotes, bookmarks, views, links, media, the isPinned, isQuote, isRetweet and isReply flags, username, fullname and a user object: 25 fields in data.tweets. Each call costs 1 credit, no X login.
How many tweets come back per call?
One page, shown in data.page_size (20 in the catalog sample). To get more, pass data.next_cursor back as cursor; null means you reached the end. Each page is one call and costs 1 credit.
Can I leave replies out?
Yes. Set with_replies to false and only the profile's own tweets are returned. The default is true. The choice is locked into the cursor, so keep it the same while you page through one profile with next_cursor.
What does include_user_info add?
With include_user_info true (the default), each tweet carries a user object: avatar, description, location, website, joinDate, verified and the follower, following, tweet, like and media totals. Set it to false for a lighter response. It is locked into the cursor.
Can I search tweets by keyword or hashtag?
No. Keyword and hashtag search is login-only on X, so this endpoint takes a profile in usernames: a handle, numeric user ID or profile URL. For a single tweet by URL, use the Twitter post endpoint.
Does Twitter Profile Scraper require an X account or login?
No. Twitter Profile Scraper uses no X account or cookies: you send your Scrapier API key in the X-API-Key header and the input, and get JSON back. Only public X data is returned, and no X developer account or API credentials are involved.
How fast does Twitter Profile Scraper run?
Scrapier does not publish a latency figure for this endpoint. Each call reads X live. Set a client timeout of 210 seconds, as the docs recommend for every endpoint, and retry a failed call, which costs nothing.
What happens if the input is wrong or X returns nothing?
If a call fails, the API returns a non-2xx status and costs 0 credits. In code, check the status, then skip that input or retry it later. Throttled calls (429 with a Retry-After header) are free as well, so retry loops cost nothing.
Does Twitter Profile Scraper work with Claude, ChatGPT and other AI agent tools?
Yes. Connect the Scrapier MCP server with claude mcp add -t http scrapier https://mcp.scrapier.io/mcp and your API key in an X-API-Key header; it works in Claude Code, Cursor and Windsurf. The agent finds twitter-tweets with search_endpoints and calls it with run_scrape. Any agent that can call an HTTP endpoint can use the REST API directly.
How much does it cost to run Twitter Profile Scraper 1,000 times?
1,000 credits, because each call is 1 credit. That is about $1.93 on Hobby, $1.58 on Pro and $1.20 on Scale, at the plans' price per credit. Failed calls are free.
How do I use Twitter Profile Scraper with Python?
Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/twitter-tweets/ with params={"usernames": "BillGates"}, your key in the X-API-Key header and timeout=210. Read r.json()["data"]["tweets"]: it is already JSON, so no HTML parsing is needed.
Is it legal to scrape X (Twitter) data?
It depends on your use and your country, so this is not legal advice. Scrapier returns public X data only. X's terms and privacy law such as GDPR or CCPA apply to how you store and use it. Collect only what you need, and ask a lawyer about your specific case.
Your feedback
Found a bug or missing a field? Let us know. Write to support@scrapier.io and the team replies to every report.
Start Scraping X (Twitter) Pages Of Tweets
Public X (Twitter) pages of tweets as JSON, 1 credit each, from REST or MCP.