Twitter (X) User Replies Timeline Scraper

Scrape a Twitter / X user's tweets-and-replies timeline by handle. For each entry you get the tweet text, the real author, the reply target, the conversation ID, engagement counts (likes, retweets, replies, quotes, bookmarks, views), language, media, and entities (mentions / hashtags / URLs). The Actor paginates the timeline by cursor until your maxItems limit is reached.

Unofficial. This Actor is not affiliated with, authorized, or endorsed by Twitter / X Corp. It is an independent tool that retrieves publicly available data via a third-party API. Use it in compliance with X's terms and all applicable laws; you are responsible for how you use the retrieved data.

What it does

• User timeline (tweets + replies) — give one or more handles (without the @). The Actor returns the conversational timeline, which interleaves the user's own tweets and their replies. Replies carry a non-null inReplyToStatusId.
• Replies only (optional) — flip repliesOnly to keep only entries that are replies.
• Cursor pagination — keeps paging via next_cursor until maxItems is hit.

Tip: pick accounts that actually reply. Handles that rarely reply (e.g. brand accounts) can return an empty timeline.

Input

Field	Type	Default	Description
screenNames	string[]	["elonmusk"]	X handles (without @) to scrape. Each is paginated independently.
maxItems	integer	28	Max total timeline entries across all handles.
repliesOnly	boolean	false	Keep only entries that are replies.

Example input

{
  "screenNames": ["elonmusk", "paulg"],
  "maxItems": 100,
  "repliesOnly": false
}

Output

One dataset item per tweet / reply:

{
  "tweetId": "2062561362719498706",
  "url": "https://x.com/elonmusk/status/2062561362719498706",
  "text": "Well said https://t.co/ks2LNlMy4C",
  "lang": "en",
  "createdAt": "Thu Jun 04 15:45:24 +0000 2026",
  "source": "<a href=\"http://twitter.com/download/iphone\">Twitter for iPhone</a>",
  "isReply": false,
  "inReplyToStatusId": null,
  "conversationId": "2062561362719498706",
  "favorites": 2462,
  "retweets": 406,
  "replies": 430,
  "quotes": 17,
  "bookmarks": 360,
  "views": 225091,
  "author": {
    "restId": "44196397",
    "name": "Elon Musk",
    "screenName": "elonmusk",
    "followersCount": 240143467,
    "blueVerified": true
  },
  "authorScreenName": "elonmusk",
  "media": { "video": [], "photo": [] },
  "entities": { "user_mentions": [] },
  "scrapedFrom": "user:elonmusk"
}

Notes

• The author of a reply entry is the actual author of that tweet, which may differ from the queried handle when the entry sits inside a conversation the user joined.
• Data is sourced live; X occasionally rate-limits, so the Actor retries transient blocks with exponential backoff.
• Tweet IDs are de-duplicated within a run.

Quick start

1. Open the Actor and press Run — the default input works out of the box.
2. Adjust the input fields below to your target (keywords, IDs, or URLs) and set maxItems to cap spend.
3. Grab results from the Dataset tab as JSON / CSV / Excel, or pull them via the Apify API and MCP from your own code.

No proxies to configure, no cookies to paste, no login — the Actor handles everything server-side.

Why teams switch to this Twitter (X) user replies scraper

Seeing how an account engages — not just what it broadcasts — needs its replies, which browser scrapers handle worst. This Actor reads a direct HTTP API and returns an account's replies with full context and engagement as clean JSON at $3 per 1,000 replies.

What people build with it

• Engagement-style analysis — how does a brand or exec actually talk to its audience? Their replies show it.
• Influencer vetting — gauge authenticity and responsiveness before a deal, beyond follower counts.
• Support auditing — review how a company handles complaints in public.
• Conversation research — study the back-and-forth that keeps high-profile threads alive.
• Dialogue datasets — reply chains from a single voice for fine-tuning.

Tips for better results

• Usernames work with or without @.
• Pair with Twitter User Tweets Scraper for original posts, and Twitter User Profile Scraper for bio and follower context.
• Engagement fields are numeric for easy ranking.

---

Why this Actor

• Direct API, no headless browser — fast, stable runs with nothing to babysit.
• No login, no cookies — we never touch your accounts, so there's no ban risk.
• Fresh, real-time data — every run reads the source live, not a stale cache.
• Pay per result — you're billed only for the rows actually delivered.
• Structured JSON — export to CSV, Excel, or JSON, or pull straight from the API / MCP.

Use cases

• Mine audience sentiment and feature requests from real comment threads.
• Surface the most-liked replies and frequent questions under any post.
• Build moderation, UGC, or social-listening datasets at scale.
• Spot superfans and detractors by author and engagement.

FAQ

Do I need an account, cookies, or to log in anywhere? No. The Actor talks to a fast, direct HTTP API server-side — you just provide inputs and run it.

How am I billed? Pay-per-result: a fixed price per row returned, with no separate platform/compute charge. Caps like maxItems keep spend predictable.

Can I run it on a schedule or call it from my app? Yes — use Apify Schedules, the REST API, the JavaScript / Python clients, or the MCP server. See the API tab.

Is this affiliated with Twitter (X)? No. It's an independent tool that collects publicly available data. Use it in line with the platform's terms and applicable law.

More Twitter (X) scrapers by us

• Twitter (X) Search — Tweet search · Top & Latest · 30+ fields
• Twitter (X) User Tweets — User timeline · stats · media
• Twitter (X) Profile — Profile · bio · follower counts
• Twitter (X) Tweet Replies — Replies & comments on a tweet

Browse the full fleet → https://apify.com/ethereal_wool