X Twitter User Profile Scraper - Posts, Followers, Views avatar

X Twitter User Profile Scraper - Posts, Followers, Views

Pricing

from $27.50 / 1,000 monitored subject re-checkeds

Go to Apify Store
X Twitter User Profile Scraper - Posts, Followers, Views

X Twitter User Profile Scraper - Posts, Followers, Views

X Twitter user profile scraper: any account's profile (followers, following, bio, location, verified type, post count) and its recent posts with text, likes, reposts, replies, quotes, views, bookmarks and date. Paste handles; JSON, CSV, Excel or API. Our fee $10 per 1,000 posts + supplier.

Pricing

from $27.50 / 1,000 monitored subject re-checkeds

Rating

0.0

(0)

Developer

Khandji Omar

Khandji Omar

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

1

Monthly active users

5 hours ago

Last modified

Features

Limited permissions

Share

X Twitter User Profile Scraper — Posts, Followers, Views

Scrape any X (Twitter) account: the profile (followers, following, bio, location, verified type, post count) and its recent posts with text, likes, reposts, replies, quotes, views, bookmarks and date. Paste handles; export to JSON, CSV or Excel or use the API. No login or X API key.

In short: what you give, what you get, what it costs

You giveX (Twitter) handles
We doRead each account's profile and its recent posts
You getThe profile (followers, following, bio, location, verified type, post count) and one row per post: text, likes, reposts, replies, quotes, views, bookmarks and date, plus every field the supplier returns (source_data)
It costs$10 per 1,000 posts, $0.29 from 21 November 2026, no start fee. Optional scheduled monitoring: +$0.05 per check, $0.005 from 21 November (one-off runs never pay it). Apify also bills the supplier Actor xquik/x-profile-scraper that this robot runs for you, at its own price (about $0.15 per 1,000 results). The first 10 results of every run are free of this robot's fee.
It does notSign in to X or need an X API key

A real result row is shown further down this page.

Free tier — 10 results free on every run

The free results waive this Actor's own fee; the source Actor (xquik/x-profile-scraper) still bills its own price for every row it returns.

The first 10 results of every run are free, on every run you ever make — not a one-off trial. Run it on your own subjects and see the real output before you are billed for a single result.

One guard: the free allowance never covers more than half of a run, so a run returning 6 results gets 3 free. That keeps the offer sustainable.

What it does

Run it once and get the full, current data as clean rows you can export to JSON, CSV or Excel, or pull through the API. Need only fresh data? Turn on monitorEnabled and schedule it: every later run returns only what is new or changed since the previous one, so you never re-download or re-pay for the same rows.

Compared with apidojo/twitter-profile-scraper

Read on the Store on 2026-10-23 (Twitter Profile Scraper: Get Profile Tweets + Their Replies). Where it does better, this section says so.

  • Data source: this Actor runs xquik/x-profile-scraper for you, then cleans and checks every row.
  • More data, measured: on @nike (2026-10-23), 56 filled fields per run here against 32 from apidojo/twitter-profile-scraper, including a profile row with followers, following, bio, location, verified type and post count.
  • This Actor's fee is free on the first results of every run, and a hard cost cap (maxTotalChargeUsd) limits it.
  • Price: about $10.15 per 1,000 in total here ($10 for this Actor + $0.15 for xquik/x-profile-scraper), $0.4 at apidojo/twitter-profile-scraper.

Why this scraper

  1. Try before you pay. The first 10 results of every run are free, on every run.
  2. Pay only for data delivered. Failed sources and failed inputs are never billed.
  3. Cost cap on this Actor's fee. Set maxTotalChargeUsd to cap this Actor's own fee; the supplier Actor is capped separately on every call, at its own price.
  4. Only-new mode. With monitorEnabled on a schedule, you get just the new or changed rows, plus a spike signal when volume suddenly jumps.
  5. Clean, normalized rows with the same field names every run, plus a RUN_SUMMARY.json — ready for spreadsheets, databases, n8n/Make/Zapier and AI agents (MCP).

Example input

{
"handles": [
"nike",
"stripe"
],
"maxTotalChargeUsd": 1.0
}

This returns the full current data right away. To receive only what is new on a schedule, add "monitorEnabled": true: the first monitored run stores a free baseline, later runs return only new or changed rows. Pin a monitorId to keep separate targets from sharing state.

Output

Each row is one post from the account (plus one profile row per account). A real row from a run on Apify (long texts are cut here and people's names hidden; your dataset has them in full):

A real row from this Actor's latest run on Apify (2026-10-24; long texts are cut and people's names hidden here, your dataset has them in full):

{
"record_id": "2065071905791500430",
"query_id": "nike",
"url": "https://x.com/Nike/status/2065071905791500430",
"text": "Our collars are popped",
"author": "(hidden here)",
"published_at": "Thu Jun 11 14:01:24 +0000 2026",
"score": 417,
"retweetCount": 41,
"replyCount": 65,
"quoteCount": 4,
"viewCount": 162661,
"bookmarkCount": 37,
"displayTextRange": [
0,
22
],
"isNoteTweet": false,
"isPinned": false,
"isQuoteStatus": true,
"isReply": false,
"isRetweet": false,
"isTranslatable": false,
"lang": "en",
"quotedTweetId": "2065071816536891421",
"type": "tweet",
"viewState": "EnabledWithCount",
"resultType": "profileTweet",
"edit_editableUntilMsecs": "1781190084000",
"edit_editTweetIds": [
"2065071905791500430"
],
"quotedTweetPermalink_displayUrl": "x.com/nikefootball/s…",
"quotedTweetPermalink_expandedUrl": "https://twitter.com/nikefootball/status/2065071816536891421",
"quotedTweetPermalink_url": "https://t.co/U2MsqgfNI6",
"author_id": "(hidden here)",
"author_followers": "(hidden here)",
"author_following": "(hidden here)",
"author_verified": "(hidden here)",
"author_isBlueVerified": "(hidden here)",
"author_isVerified": "(hidden here)",
"author_profilePicture": "(hidden here)",
"author_profilePictureOriginal": "(hidden here)",
"author_coverPicture": "(hidden here)",
"author_description": "(hidden here)",
"author_location": "(hidden here)",
"author_createdAt": "(hidden here)",
"author_statusesCount": "(hidden here)",
"author_mediaCount": "(hidden here)",
"author_protected": "(hidden here)",
"author_url": "(hidden here)",
"author_favouritesCount": "(hidden here)",
"author_isTranslator": "(hidden here)",
"author_possiblySensitive": "(hidden here)",
"author_verifiedType": "(hidden here)",
"author_hasGraduatedAccess": "(hidden here)",
"author_parodyCommentaryFanLabel": "(hidden here)",
"author_profileImageShape": "(hidden here)",
"author_profileTranslatorType": "(hidden here)",
"author_superFollowEligible": "(hidden here)",
"quoted_tweet_text": "Dear Football, Eric Cantona has a message for you... https://t.co/DV1lE793Y2",
"quoted_tweet_retweetCount": 63,
"quoted_tweet_replyCount": 16,
"quoted_tweet_likeCount": 353,
"quoted_tweet_quoteCount": 6,
"quoted_tweet_viewCount": 196067,
"quoted_tweet_bookmarkCount": 71,
"quoted_tweet_displayTextRange": [
0,
52
],
"quoted_tweet_edit_editableUntilMsecs": "1781190062000",
"quoted_tweet_edit_editTweetIds": [
"2065071816536891421"
],
"quoted_tweet_isNoteTweet": false,
"quoted_tweet_isPinned": false,
"quoted_tweet_isQuoteStatus": false,
"quoted_tweet_isReply": false,
"quoted_tweet_isRetweet": false,
"quoted_tweet_isTranslatable": false,
"quoted_tweet_possiblySensitive": false,
"quoted_tweet_url": "https://x.com/nikefootball/status/2065071816536891421",
"quoted_tweet_createdAt": "Thu Jun 11 14:01:02 +0000 2026",
"quoted_tweet_author_id": "(hidden here)"
}
FieldWhat it holds
resultTypeprofile (the account) or profileTweet (a post)
textpost text, or the bio on the profile row
published_atpost time, or the account creation date on the profile row
scorelikes
retweetCountreposts
replyCountreplies
quoteCountquotes
viewCountviews
bookmarkCountbookmarks
langlanguage
followersfollowers (profile row)
followingfollowing (profile row)
statusesCounttotal posts (profile row)
locationlocation (profile row)
isBlueVerifiedblue check (profile row)
verifiedTypeBusiness, Government... (profile row)
urlpost link, or the website on the profile row

Each row also keeps the other fields the source returns, so you get everything above and more. In the Output tab, the Overview table shows these columns, readable without any code; export them as CSV, Excel, JSON or HTML.

Also in the rows when X shows them (seen in this Actor's real runs): accountBasedIn (country, how precise, when observed), connectedVia (how the account joined), identityVerification (ID-verified and since when), verificationReason, usernameChanges (count), creatorSubscriptionsCount, businessAccountAffiliatesCount, profileDescriptionLanguage, highlightsInfo, and for a retweet the original tweet in retweeted_tweet (text, author, date, link) with retweetedAt.

Every supplier field included

Each row also carries source_data: the full row returned by xquik/x-profile-scraper, every field it gives, untouched — you never get less than the supplier itself delivers. Our own fields above stay exactly as they are. A row over 200 KB is trimmed and source_data_trimmed lists the fields cut.

How you're charged

  • Source Actor charge: this Actor runs xquik/x-profile-scraper inside your run, and Apify bills that run to your account at xquik/x-profile-scraper's own price (about $0.15 per 1,000 results, read on 2026-10-23), on top of this Actor's price. Each call to it is capped at $0.50.
  • Result — $0.01 per post from 22 October 2026 (free before that date), billed only for results delivered to your dataset. With monitoring on, only results that are new since the last check are delivered and billed.
  • Monitoring check ($0.05) — only when you turn on scheduled monitoring (monitorEnabled), once per target per run, and only when the source responded. One-off runs never pay it: you pay only per result.
  • One-off runs pay only per result. The monitoring check applies only to scheduled monitoring; every call to the supplier Actor is capped per call, at its own price, and maxTotalChargeUsd caps this Actor's own fee.

How to use it in 3 steps

  1. Click Try for free and fill in X/Twitter handles (handles).
  2. Optional: adjust the other fields; every one has a description and a sensible default.
  3. Click Start and download the results as JSON, CSV or Excel, or read them from the API.

Use cases

  • Influencer
  • Competitor research

Use it from code (API)

Every Apify Actor is an API. Start a run and read the results with one call.

Python

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("om_kh/twitter-x-profile-scraper").call(run_input={"handles": ["nike", "stripe"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('om_kh/twitter-x-profile-scraper').call({
"handles": [
"nike",
"stripe"
]
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call (cURL) — runs the Actor and returns the dataset in the same response:

curl -X POST "https://api.apify.com/v2/acts/om_kh~twitter-x-profile-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"handles": ["nike", "stripe"]}'

Integrations: n8n, Make, Zapier, Google Sheets

  • n8n — the official Apify node, operation Run Actor and get dataset, Actor om_kh/twitter-x-profile-scraper.
  • Make — Apify › Run an Actor, then Apify › Get Dataset Items.
  • Zapier — Apify › Run Actor; map the dataset items into your next step.
  • Google Sheets, webhooks, Slack — add an integration from the Integrations tab of this Actor.
  • Schedules — run it every hour or day from Schedules in Apify Console.

Use it from an AI agent (MCP and x402)

Connect Claude Desktop, Cursor, VS Code or any MCP client to Apify's MCP server at https://mcp.apify.com and add this Actor, om_kh/twitter-x-profile-scraper, as a tool — the agent passes the same JSON as the run input and gets the dataset back.

AI agents that pay with x402 can run it too, without an Apify account: the Actor charges only per result delivered, so an agent pays exactly for what it gets.

FAQ

Is it legal to scrape X (Twitter)? This Actor collects only publicly available X (Twitter) data and never logs in. You are responsible for how you use it; check X (Twitter)'s terms and your local law (GDPR, CCPA) if you store personal data, and ask a lawyer if unsure.

Do I need an account, cookies or an API key? No. You only need an Apify account to run it.

What data do I get? The account's posts with text, likes, reposts, replies and date. Download it as JSON, CSV, Excel, HTML or XML, or read it from the API.

Am I charged when something fails? No. An input that fails is listed with its reason in the run summary and is never charged.

Can I run it on a schedule? Yes. Create a schedule in Apify Console (hourly, daily, weekly) and connect webhooks, Google Sheets, Slack, n8n, Make or Zapier.

Can I use it from Python, JavaScript or an AI agent? Yes: see the code samples above, or connect AI agents through MCP with the x_profile_new_posts tool.

All input fields

The main fields are described above; these are the others the form accepts:

  • currentItems (Bring your own posts (optional)) — Skip the chained fetch and pass posts directly (no upstream call, no fetch fee).

Your feedback

Did this Actor save you time? A short review on the Reviews tab helps other people find it, and every review is read. Something missing or broken? Open an issue on the Issues tab: it is answered and fixed fast.

More Actors from the same author