X (Twitter) Retweeters Scraper

X (Twitter) Retweeters Scraper

X (Twitter) Retweeters Scraper is an Apify Actor for people and workflows that need to identify who retweeted a public X post. It accepts either one or more public Tweet URLs or numeric Tweet IDs, and it returns one record per retweeter profile. Each record can include username, display name, bio, follower count, following count, blue verification status, profile URL, and the source tweet URL, so the result is easy to use for audience review, outreach lists, and analysis pipelines.

This Actor is available through Apify and usable through Apify MCP. It is provider-backed, cookieless, and does not require login.

Best fit and connected workflows

This Actor fits workflows where the source of truth is a public post and the goal is to see who amplified it. Common routing patterns include:

• Starting from a public post URL when you already know the exact tweet you want to inspect.
• Starting from a raw tweet ID when an upstream agent, spreadsheet, or API process has already extracted the ID.
• Using the returned profile records as a clean input set for lead generation, audience mapping, or manual review.
• Running it alongside other X-focused Actors in a broader research workflow, where one step collects the post and this Actor collects the retweeters.

Example scenario

Maya works in partnerships and has a public post from a competitor that received strong engagement. She pastes the post URL into the Actor and sets a cap on retweeters per tweet. The output returns usernames, display names, bios, follower counts, blue verification flags, profile URLs, and the source tweet URL. Maya uses those fields to review which accounts amplified the post, then moves qualified profiles into a follow-up outreach list.

Input

Use either tweetUrls or tweetIds. The schema is designed so one record can represent one or more public posts, and each post can return multiple retweeter profiles.

Field	Type	Required	Description
tweetUrls	array of strings	No	One or more public X/Twitter post URLs. Accepts x.com or twitter.com URLs. Use this field or tweetIds, with one input path per run.
tweetIds	array of strings	No	Numeric tweet IDs as an alternative to full URLs. Useful when an upstream process already has the raw ID.
maxRetweetersPerTweet	integer	No	Maximum number of retweeter profiles to return for each tweet. Default: 500. Minimum: 1. Maximum: 10,000. Each provider page can return up toa bounded number of users.

Focused JSON input example

{
  "tweetUrls": [
    "https://x.com/NASA/status/1842633697437560908"
  ],
  "maxRetweetersPerTweet": 100
}

Output

The dataset view is called Retweeters. Each item represents one retweeter profile for one source tweet.

Field	Type	Description
username	string	X handle without the @ symbol.
display_name	string	Profile display name.
bio	string	Public profile bio text.
follower_count	number	Followers on the retweeter profile.
following_count	number	Accounts the profile follows.
is_blue_verified	boolean	Blue verification status.
profile_url	string	Direct link to the profile.
tweet_url	string	Source tweet URL that produced the record.

Illustrative dataset record

{
  "username": "johndoe",
  "display_name": "John Doe",
  "bio": "Growth and product",
  "follower_count": 12400,
  "following_count": 853,
  "is_blue_verified": true,
  "profile_url": "https://x.com/johndoe",
  "tweet_url": "https://x.com/NASA/status/1842633697437560908"
}

How it works

The Actor is provider-backed. The live contract shows a primary ScrapeCreators path with a live endpoint coverage check and a SociaVault fallback. It runs cookieless and without login. The input is resolved from either Tweet URLs or Tweet IDs, and the Actor pages through provider results in batches of up toa bounded number of users per page until it reaches your maxRetweetersPerTweet cap.

The Actor writes results to the default dataset and also exposes summary records in key-value storage:

• OUTPUT
• RUN_SUMMARY

Pricing

X (Twitter) Retweeters Scraper uses Pay per event plus Apify platform usage. The live pricing tab is the source of truth for current pricing details: Pricing tab.

The event model in the live contract includes:

• Actor start
• Retweeter found

As a simple planning example, if a run returns one hundred retweeters, the cost is based on one actor start event plus one hundred retweeter-found events, together with Apify platform usage.

Use with AI agents (MCP)

This Actor can be called as an Apify MCP tool for agent workflows that need retweeter profiles from a public X post.

Tool description: retrieve retweeter profiles for one or more public X/Twitter posts, with fields such as username, display name, bio, follower count, following count, blue verification status, profile URL, and source tweet URL.

Actor identity: khadinakbar/x-retweeters-scraper

Use the Apify Actor khadinakbar/x-retweeters-scraper to extract retweeter profiles from a public X post. Provide either tweetUrls or tweetIds, and set maxRetweetersPerTweet if I want to cap the result count. Return the dataset rows and summarize the profiles for outreach review.

Output interpretation:

• Each dataset row is one retweeter profile.
• tweet_url ties a profile back to the source post.
• profile_url is the profile destination for follow-up review.
• is_blue_verified helps filter for blue-verified accounts when that is useful in a workflow.

Provenance and scope:

• The Actor returns public retweeter profiles from the supplied post input.
• The result set reflects the configured cap per tweet.
• The output is suited to machine reading in MCP because each row is already normalized into dataset records.

Pagination and cost guidance:

• The provider returns results in pages of up toa bounded number of users.
• Larger caps may retrieve more pages and more charged events.
• Smaller caps are useful when you only need a sample set for analysis or enrichment.

Apify API example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
    token: process.env.APIFY_TOKEN,
});

const input = {
    tweetUrls: ['https://x.com/NASA/status/1842633697437560908'],
    maxRetweetersPerTweet: 50,
};

const run = await client.actor('khadinakbar/x-retweeters-scraper').call(input);

const { items } = await client.dataset(run.defaultDatasetId).listItems();

console.log(items);

Set APIFY_TOKEN in your environment before running the example.

Best results and outcome guidance

Use the exact public post URL or the raw tweet ID for the post you want to inspect. If your workflow already holds tweet IDs, tweetIds is a clean input path for agent and API use. If you only need a sample, set a lower maxRetweetersPerTweet; if you need broader coverage for a single post, increase the cap within the schema range.

For downstream analysis, the most useful fields are usually:

• username
• display_name
• bio
• follower_count
• is_blue_verified
• profile_url
• tweet_url

Focused standalone workflow

X (Twitter) Retweeters Scraper is designed as a focused standalone workflow for the public input and structured output contract described above.

Design note

I found that the live dataset view is built around a compact set of profile fields, with username, display_name, bio, follower_count, following_count, is_blue_verified, profile_url, and tweet_url exposed in the table view. That makes the output straightforward to read and pass into other workflows.

FAQ

Can I start from a tweet ID instead of a URL?

Yes. The input schema supports tweetIds as an alternative to tweetUrls.

What does one output record represent?

One output record represents one retweeter profile for one source tweet.

How do I control result volume?

Use maxRetweetersPerTweet to set the per-tweet cap.

Is this Actor usable in Apify MCP workflows?

Yes. It is an Apify Actor that can be invoked through Apify MCP.

Where should I check current pricing details?

Use the live Pricing tab for the current pricing view.

Responsible use

X and Twitter is a trademark of its owner. This independent Actor is not affiliated with, associated with, or endorsed by X and Twitter.

Use this Actor in a way that respects applicable laws, platform rules, and privacy expectations for public data workflows.