X (Twitter) Replies Retweets Scraper

What does this Twitter replies and retweets scraper do?

This Actor helps you extract Twitter / X replies, retweets, tweet details, and retweet-check results from public tweets when you already know the tweet URL or tweet ID. It is designed for fast, targeted collection, not broad keyword search.

The easiest way to try it is simple: paste one or more tweet URLs or numeric tweet IDs into the input, choose a single category such as replies, retweets, info, or checkRetweet, and run the Actor. The Actor automatically extracts the numeric tweet ID from each URL and processes every input tweet with that one category.

If you need a reliable Twitter data workflow, the Actor also benefits from the full Apify platform package:

• 🚀 run it manually or on a schedule
• 📦 save output to an Apify dataset
• 🔌 use it through API, webhooks, and integrations
• 📊 monitor run history, logs, and failures
• ♻️ repeat the same setup for regular Twitter data collection

Why use this Twitter scraper?

This Actor is useful when you want focused tweet-level data without building your own pipeline.

Common use cases:

• 💬 collect replies to a tweet for sentiment analysis, moderation review, or lead discovery
• 🔁 extract retweets for social proof tracking and campaign monitoring
• ℹ️ save the full tweet info object for analytics or archiving
• ✔️ check whether a specific username retweeted a specific tweet
• 🧵 process multiple tweet URLs in one run while keeping category order predictable
• 📤 export structured results to JSON, CSV, Excel, XML, or HTML for dashboards, CRM workflows, spreadsheets, or AI pipelines

It is especially useful for users who already have tweet links from spreadsheets, CRM exports, monitoring tools, or manual research and want to turn them into structured output quickly.

What can this Twitter replies scraper extract?

The exact fields depend on the selected category and the underlying tweet data, but the Actor commonly returns data like this:

Category	Typical fields
Replies	id, tweet_id, created_at, text, full_text, screen_name, name, engagement fields
Retweets	id, tweet_id, screen_name, name, profile-related fields, engagement fields
Tweet info	tweet text, author details, counters, media-related fields, language, timestamps
Check retweet	raw check result fields such as is_retweeted or equivalent response fields

Every dataset item also includes a metadata object added by the Actor, for example:

• metadata.category
• metadata.sourceInput
• metadata.sourceTweetId
• metadata.sourceTweetUrl
• metadata.page
• metadata.position
• metadata.screenname for checkRetweet

This gives you both: the raw response fields at the top level and your own processing context grouped cleanly under metadata.

How to scrape Twitter replies, retweets, and tweet info

You do not need coding knowledge to use this Actor.

1. Open the Input tab.
2. Paste one or more tweet URLs or numeric tweet IDs into urls.
3. Choose one category.
4. Set resultsPerCategory if you want to limit replies or retweets.
5. Turn on parseAllResults if you want to keep paginating until the source has no more results.
6. If you selected checkRetweet, fill in retweetCheckUsername.
7. Run the Actor and open the Output tab when the run finishes.

The Actor processes one tweet at a time. The selected category is applied to every tweet in the run.

Input example

Twitter replies scraper has the following input options. Click on the Input tab in Apify Console for the live form and field help.

{
    "urls": ["https://x.com/apify/status/2021770553154285890", "2021770553154285890"],
    "category": "replies",
    "resultsPerCategory": 100,
    "parseAllResults": false,
    "retweetCheckUsername": "elonmusk"
}

Input notes:

• 🔗 urls accepts both full tweet URLs and plain numeric tweet IDs
• 🗂️ category accepts one value per run
• 🔢 resultsPerCategory applies to replies and retweets
• ♾️ parseAllResults ignores the per-category limit and keeps paginating
• ✔️ retweetCheckUsername is only used when checkRetweet is selected

Output example

You can download the dataset extracted by this Actor in various formats such as JSON, CSV, Excel, XML, or HTML.

Example reply item:

{
    "metadata": {
        "category": "replies",
        "sourceInput": "https://x.com/apify/status/2021770553154285890",
        "sourceTweetId": "2021770553154285890",
        "sourceTweetUrl": "https://x.com/i/status/2021770553154285890",
        "page": 1,
        "position": 1
    },
    "id": "1900000000000000001",
    "tweet_id": "1900000000000000001",
    "created_at": "Wed Mar 12 12:34:56 +0000 2025",
    "screen_name": "example_user",
    "name": "Example User",
    "text": "Interesting point.",
    "full_text": "Interesting point. Here is the full reply text."
}

Example checkRetweet item:

{
    "metadata": {
        "category": "checkRetweet",
        "sourceInput": "2021770553154285890",
        "sourceTweetId": "2021770553154285890",
        "sourceTweetUrl": "https://x.com/i/status/2021770553154285890",
        "screenname": "elonmusk"
    },
    "is_retweeted": false
}

How much does it cost to scrape Twitter data?

The exact cost depends on:

• how many tweet URLs or IDs you submit
• which category you select
• whether you enable parseAllResults
• how much pagination is needed for replies or retweets

In practice, this Actor is usually efficient because it performs targeted tweet-level requests instead of crawling the entire website. Small test runs are typically inexpensive, and you can use the Apify platform to scale up later with scheduling, API access, and integrations.

If you are comparing options, the easiest way to estimate price is to test a small batch first, then scale once you know the average number of pages needed for your target tweets.

You can monitor actual run usage directly in Apify Console, including run history and resource consumption, and compare plans on the Apify pricing page. That makes it easy to estimate the cost of processing 10 tweets versus 1,000 tweets before committing to larger scheduled workloads.

Tips for better results

• 🎯 Use direct tweet IDs when you already have them
• 📉 Keep resultsPerCategory low for quick test runs
• ♻️ Turn on parseAllResults only when you truly need full pagination
• ✔️ Use checkRetweet only when you need user-specific confirmation
• 📁 Store your output in Apify datasets and automate follow-up processing with the Apify API or integrations

Other Twitter Actors

If you work with Twitter / X data regularly, you may also want these Actors:

• X / Twitter Advanced Search for discovering tweets by keywords, filters, accounts, and search operators before you collect replies or retweets from specific tweet IDs.
• X / Twitter Followers Scraper for extracting follower lists and account-level audience data when your workflow starts from a profile instead of a tweet.

FAQ

Is this Actor a full Twitter search scraper?

No. This Actor is for tweet-level extraction when you already know the tweet URL or tweet ID. If you need keyword or account-level discovery, use a search-focused Actor instead.

What happens if checkRetweet is selected without a username?

The Actor logs a warning and skips that category. The rest of the selected categories can still run normally.

Does the Actor retry failed requests?

Yes. The Actor retries failed or empty list responses up to three times and logs what it is doing, which helps make runs more reliable.

Is scraping Twitter / X legal?

Our scrapers are intended to collect publicly available data. They are not designed to extract private account data. However, your results may still contain personal data, and laws such as GDPR or other local regulations may apply to how you store and use that data. You are responsible for making sure your use case is lawful and compliant in your jurisdiction.

Where can I get help or request improvements?

If you need help, check the run logs first because they explain category processing, retries, pagination, and skipped checks. The Actor also has a dataset schema configured, so the Output tab should be readable immediately after a run. You can use the Actor's Issues tab to report bugs, request features, or suggest improvements. If you need a custom Twitter workflow, feel free to reach out through the Apify Store profile.