Threads User Reposts Scraper

Collect public reposts from a Threads profile's Reposts tab and export structured rows for review and download.

Use this Actor when you want to see what a public Threads user has reshared — who they reposted, when they reposted it, and the original post behind each repost with its available public details.

Looking for a user's own posts, profile, or Threads search instead? Try the companion Threads Scraper — Posts, Profiles & Search.

Explore more FuturizeRush Actors

What You Get

• Public repost rows from Threads profile Reposts tabs
• The reshared original post's public details on the same row: author, text, content type, timestamp, available engagement counts, media links when present, mentions, hashtags, and URLs
• Reposter details: username, display name, follower count when available, and the time the post was reshared
• Direct source URLs for both the repost and the original post
• A run summary with saved row counts and completion status

How to Use

1. Paste one or more Threads profile URLs, Reposts tab URLs, or usernames.
2. Choose the maximum number of public repost rows to save per profile.
3. Start the Actor.
4. Review the default dataset view or download the results in your preferred format.
5. Open the run summary when you need saved row counts or completion status.

Input

You can provide profile URLs, Reposts tab URLs, usernames, or a mix of them. Use up to 20 profiles per run. max_reposts_per_profile accepts 10 to 5,000 and is a per-profile cap, not a promised result count. Use a larger value when you want the run to keep looking for public reposts until the selected cap is reached or no more public reposts are available during the run.

{
  "profiles": [
    "https://www.threads.com/@natgeo"
  ],
  "max_reposts_per_profile": 20
}

Output

Each saved row represents one public repost made by the requested profile, together with the reshared original post's available public details. The dataset is organized around three practical views, described under Dataset Views below.

Short Output Example

This synthetic, shortened example shows the most important fields. The Dataset schema defines the full export field list.

{
  "record_type": "repost",
  "input_username": "sample_profile",
  "profile_username": "sample_profile",
  "profile_user_id": "10000000001",
  "reposted_at": "2026-01-20T09:15:00Z",
  "repost_url": "https://www.threads.com/@sample_profile/post/EXAMPLE_REPOST_ID",
  "conversation_index": 1,
  "original_post_url": "https://www.threads.com/@example_author/post/EXAMPLE_ORIGINAL_ID",
  "original_author_username": "example_author",
  "original_author_id": "10000000002",
  "original_author_display_name": "Example Author",
  "original_author_is_verified": true,
  "original_content_type": "image",
  "original_content_preview": "A short look at today's highlights.",
  "original_text": "A short look at today's highlights.",
  "original_created_at": "2026-01-18T14:02:00Z",
  "original_like_count": 1280,
  "original_reply_count": 46,
  "original_repost_count": 88,
  "original_quote_count": 12,
  "original_share_count": 30,
  "original_view_count": null,
  "original_view_count_status": "not_checked",
  "original_has_media": true,
  "original_media_type": "image",
  "original_media_url": "https://example.com/media/EXAMPLE_ORIGINAL_ID.jpg",
  "original_mentions": ["example_partner"],
  "original_mentioned_accounts": [{ "username": "example_partner", "user_id": "10000000003" }],
  "original_hashtags": ["highlights"],
  "original_urls": [],
  "source_tab": "reposts",
  "scraped_at": "2026-01-20T09:20:00Z"
}

Fields that start with profile_ describe the profile that reshared the post. reposted_at is when it was reshared. Fields that start with original_ describe the original post that was reshared. original_text contains only visible text; media, GIFs, and stickers are represented by their own fields. profile_user_id and original_author_id are stable numeric account ids that stay the same even if the account is renamed. original_mentioned_accounts pairs each structured mention in the original post with the mentioned account's stable id for the same reason, alongside the plain original_mentions handle list. The view count status field distinguishes an original post whose view count was read this run (available) from one where this reposts feed did not carry a view count that run (not_checked — this does not mean the post has no views).

conversation_index is the saved result order for the requested profile.

Dataset Views

• 🔁 Repost Review: the default view for reading each repost next to a preview of the original post
• 📊 Engagement: available public counts for each reshared original post, including view count status
• 🔗 Original Media & Links: media, stickers, URLs, mentions, and hashtags from the original post

Main dataset fields include the requested profile, the repost time, the original author, original content type, original preview and text, original post URL, available original engagement counts, view count status, media links when present, stickers when present, mentions, hashtags, and source timestamps. The dataset schema defines the complete field list for exports and advanced workflows.

Common Use Cases

• Social listening and community research
• Understanding what a creator or brand amplifies
• Content curation and trend discovery
• Audience and engagement analysis
• Public Threads research datasets

FAQ

Does this collect private content?

No. It is designed for public Threads profile pages and saves only public content that is available at run time.

What exactly is a repost here?

A repost is a post the requested profile reshared from another author on their public Reposts tab. Each saved row carries the reshared original post's public details in the original_* fields, so you can review the original without a separate lookup.

Can I choose how many reposts to save?

Yes — set Max reposts per profile. The value is a cap, not a promised result count: the Actor saves the public reposts exposed on the profile's Reposts tab at run time, and the final run summary reports how many were actually saved. A profile with few public reposts will return fewer rows.

Why can original_text be empty?

original_text contains only visible text. An original post can still be valid when it is image-only, GIF-only, sticker-only, quote-only, or otherwise has no visible text. Use original_content_type, original_content_preview, original_media_url, original_media_urls, original_sticker_urls, and original_quoted_post_url to review those rows.

Why are some fields empty or null?

Some public pages expose different metrics or media details across rows. Unavailable text fields are saved as empty strings, while unavailable numeric or optional fields may be null.

Why can the number of reposts differ slightly between runs?

A profile's public Reposts tab is live. The profile can reshare new posts or remove older ones at any time, and a reshared original can be momentarily unavailable and then return. Each run captures the reposts that are publicly visible at that moment, from the newest ones up to the limit you set (or the profile's earliest public repost, whichever comes first). A small difference between runs usually reflects these real changes on the profile, or the momentary public availability of individual posts — for a point-in-time list, use the most recent run.

What if a run ends early or returns fewer results than expected?

Threads sometimes limits how much public content it serves at busy moments, which can cut a run short. If that happens, you can run it again, split a large list into smaller runs, or space runs out.

Can I use profile URLs instead of usernames?

Yes. You can paste profile URLs such as https://www.threads.com/@zuck, Reposts tab URLs such as https://www.threads.com/@zuck/reposts, or usernames in the profiles field.

Related Actors

This Actor collects the reposts made by a public profile. For posts, profiles, and search, or for replies, use the related Actors below.

• Threads Scraper — Posts, Profiles & Search
• Threads Replies Scraper

Disclaimer

This Actor is intended for collecting publicly available Threads data for legitimate research, monitoring, and analysis.

• It is not affiliated with Threads, Meta, or Instagram.
• It does not collect private content.
• Public availability, structure, and completeness can change moment to moment; a run that ends early can be retried.
• Review your use case, applicable laws, platform terms, and privacy obligations before using or sharing collected data.

Keywords

Threads scraper, Threads user reposts scraper, Threads reposts, Threads reshares, Threads profile reposts, Threads social listening, Threads engagement analysis, Threads audience research, Threads content curation, Apify Threads Actor, Claude Code, OpenClaw, Gemini, Antigravity, Codex, ChatGPT