App Logo
x.com

See who reposted (retweeted) a post on X (Twitter)

TL;DR

Each reposter comes back as one row with followers, following, bio and website.

About

X already lists who reposted a public post on its Reposts tab (the post URL plus /retweets), but only as a feed you scroll by hand. get_reposters opens that tab, keeps scrolling, and turns each account into a row you can sort. The count input defaults to 100 and goes up to 1,000, so raise it for a busy post. A founder whose launch post picked up 180 reposts runs it with count at 200, sorts by followers, and finds four accounts with large followings next to a cluster of blank-bio accounts each following about 5,000 people, which looks a lot like an engagement pod. Those four go into a private X List (create_list, then add_to_list per handle) so the founder can watch what they post next. The catch is that X serves a sample of reposters rather than the full set, so on a viral post the list stops a few hundred in whatever count you ask for.

Input

url optional

Full URL of the X post, e.g. 'https://x.com/<handle>/status/<id>'. Query/hash are stripped.

urls optional

Not supported since 19 Oct 2026: the run fails with a message saying so. Send one url per call and fan out with run_script's scripts.

count optional

Max reposters to return. Scrolls until count is met or the list dries up. Default 100.

Default: 100

Output

url optional
count optional

Number of reposters returned. 0 is a first-class outcome (no reposts, or reposters hidden).

complete optional

True only when X marked the end of the list and every reposter fits in count. X shows a sample of reposters, so a long list can end before the repost total.

reposters optional
account_used optional

Handle of the signed-in account that performed this lookup, read from the page.

Example output

Shape only: placeholder values generated from the output schema, not a real run.

{ "url": "https://example.com/item/123", "count": 3, "complete": true, "reposters": "…", "account_used": "…" }

FAQ

List the accounts that reposted (retweeted) an X post, by post URL. Returns per account: user_id, handle, name, followers, following, tweets, verified, location, website, bio. X returns a sample of reposters, not the full set: high-repost posts cap out a few hundred deep.
Optional: url, urls, count.
It returns url, count, complete, reposters, account_used.
Yes. It acts as you on x.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the x.com cookies saved by the Reduck extension.
It only reads. It looks things up on x.com and changes nothing there.
Ask an AI agent connected to Reduck to run reduck/x.com/get_reposters, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/x.com/get_reposters
It is part of Reduck's official curated catalogue.
The count input defaults to 100, so a post with 250 reposts returns 100 rows unless you raise it (1,000 is the max). Past that, X serves only a sample of reposters and the list dries up a few hundred deep however high you set count. Asking for more than X will serve costs nothing but a short wait, because the run ends once three scrolls in a row bring no new accounts.
get_reposters covers reposts only. Quotes have their own script, get_quote_tweets, which returns each quoting tweet with its text and post time. Likes have been private on X since June 2024, visible only to the post's author, and Reduck has no script that exports likers.
On X's pay-per-use plan each user returned is billed as a user read at $0.010, so a full page of 100 reposters costs about $1 in credits bought upfront, and a user already billed that UTC day is not charged again. X's integration guide also says the retweeted_by endpoint returns only the 100 most recent reposting users, at 75 requests per 15 minutes, so paying more does not get you further down the list.
get_reposters returns no repost time. Each row is a profile only and the order is whatever X serves, so the output cannot rank reposters by time or tell you whether the reposts came in one burst. Quote tweets are different: get_quote_tweets returns a created_at for each quoting tweet.

Related scripts

x.com

Search X (Twitter) posts

Search X (Twitter) for tweets with every X search operator, from the Top tab (a ranked sample, the default) or the Latest tab (chronological), picked by the tab arg. Returns per tweet a canonical record: id, url, author {id, handle, name}, text, created_at, lang, likes, retweets, replies, quotes, bookmarks, views, is_retweet, is_quote, plus followers (the author's follower count, a search-only enrichment), and the top-level query and count. Top is a ranked sample, not exhaustive.

x.com

Get a tweet and its replies on X (Twitter)

Get a tweet on X (Twitter) by URL, with the conversation around it: `tweet` (the post itself) and `replies` (every other post of its conversation on the page: the thread above it when it is a reply, and the replies below; use in_reply_to to rebuild the thread). Each post has id, url, author, text, created_at, lang, counts, in_reply_to and quoted_tweet. With count, it loads more replies until it has count or X reaches the end. complete is true only when X reached the end and left no folded replies (Show replies, hidden or probable-spam sections), which this script does not open. A deleted or unavailable tweet is an error. Requires being signed in to X.

x.com

Get X (Twitter) user profile

Look up an X (Twitter) user's profile by handle. Returns handle, user_id, name, bio, location, website, joined, followers_count, following_count, is_verified, is_self, is_following, follows_you. Counts are exact integers. bio and website carry the real destination URLs, with X's shortlinks resolved. is_following is null on your own profile. Any of is_self, is_following, follows_you and is_verified is null when X does not say. Requires being signed in to X; a missing or suspended account is an error that says which.

Start building not clicking

Get started for free