X (Twitter) Tweet Replies Scraper — Comments & Sentiment avatar

X (Twitter) Tweet Replies Scraper — Comments & Sentiment

Pricing

from $1.00 / 1,000 reply results

Go to Apify Store
X (Twitter) Tweet Replies Scraper — Comments & Sentiment

X (Twitter) Tweet Replies Scraper — Comments & Sentiment

Extract every reply under any X (Twitter) post — full text, author, and engagement metrics. Perfect for sentiment analysis, brand monitoring, and community research.

Pricing

from $1.00 / 1,000 reply results

Rating

0.0

(0)

Developer

Andrew

Andrew

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Extract every reply under any X (Twitter) post — full text, author, and engagement metrics. Perfect for sentiment analysis, community research, and brand monitoring.

What you get

  • Reply text, ID, URL, and creation timestamp
  • Engagement metrics — likes, retweets, replies, quotes, views, bookmarks
  • Author details — username, display name, follower count, verification
  • Conversation ID and inReplyTo context for thread reconstruction
  • Cursor-based pagination — capture huge reply threads across multiple runs

Use cases

  • Sentiment analysis on a tweet, announcement, or product launch
  • Find detractors or advocates in a brand conversation
  • Lead generation — surface engaged users on a competitor's post
  • Community research — map the audience reacting to a topic
  • Crisis monitoring — capture reply storm before tweets get deleted

How to use

  1. Enter a Tweet ID or URL (numeric ID or https://x.com/user/status/...)
  2. Choose Sort OrderRelevance (default), Latest, or Likes
  3. Set Max Replies (default 100; 0 for unlimited)
  4. Run the actor — one reply per row in the Dataset tab
  5. To fetch more replies, open the Key-value store tab → copy the NEXT_PAGE_ID value → paste it into Page ID on your next run

Output format

One reply per dataset row — perfect for direct CSV, Excel, or Google Sheets export:

{
"parentTweetId": "1846987139428634858",
"tweetId": "1847001234567890",
"url": "https://x.com/replyuser/status/1847001234567890",
"text": "Reply text here…",
"createdAt": "Wed Jan 01 12:05:00 +0000 2026",
"lang": "en",
"likeCount": 42,
"replyCount": 3,
"viewCount": 1500,
"inReplyToId": "1846987139428634858",
"inReplyToUsername": "elonmusk",
"conversationId": "1846987139428634858",
"authorUsername": "replyuser",
"authorIsBlueVerified": false,
"authorFollowersCount": 1250
}

Pagination

If the thread has more replies than Max Replies allows, the actor saves a resume cursor to the default Key-value store under the key NEXT_PAGE_ID.

  1. Open the Key-value store tab on the run page
  2. Copy the value of NEXT_PAGE_ID
  3. Start a new run and paste it into Page ID

When NEXT_PAGE_ID is null, all replies have been fetched.

Input options

FieldTypeDescription
Tweet ID or URLstringNumeric ID or full tweet URL (required)
Sort OrderselectRelevance (default), Latest, or Likes
Max RepliesintegerCap per run — default 100, 0 for unlimited
Page IDstringNEXT_PAGE_ID from the previous run's Key-value store, to resume pagination