🧵 Threads Scraper — Profiles, Keyword Search & Full Reply Threads

Pull Meta Threads posts by profile, keyword or post URL — 43 data points per post. Whole profiles (hundreds of posts, not just the first screen), full reply threads, @mentions, shared links, quotes and engagement. No login, no account, no API key.

⚡ Fast	400 posts from two profiles in about 28 seconds; 200 replies from two posts in about 14.
📜 Deep	Profiles and reply threads go as far back as you ask (maxResultsPerQuery), not just the first screen.
🔍 3 ways in	By profile, by keyword search, or by post URL with its replies.
🏷 Mentions, links & quotes	@accounts, shared URLs and quoted posts come out in their own fields.
💬 Conversation aware	replyToUsername and rootPostUsername reconstruct who is answering whom.
🔓 No credentials	Nothing to sign up for, no cookies to paste.

---

What data does it extract?

🧵 Posts

Core: id, code, url, text, createdAt, queryContext

Engagement: likeCount, replyCount, repostCount, quoteCount, reshareCount

Author: authorUsername, authorFullName, authorIsVerified, authorProfilePicUrl, authorId

Mentions & links: mentions (every @account named in the post), links (every URL shared, with its display text), linkPreviewUrl, linkPreviewTitle, linkPreviewDomain

Quotes & reposts: quotedPostUrl, quotedPostAuthor, quotedPostText, repostedPostUrl — a quoted post stays attached to the post that quotes it instead of appearing as a separate row

Conversation: isReply, replyToUsername, rootPostUsername, replyControl, isLikedByRootAuthor, isPinnedToProfile, isRootPost (post mode)

Media: mediaType, mediaTypeLabel, mediaUrls, mediaWidth, mediaHeight, hasAudio

Signals: detectedLanguage, isEdited, isPaidPartnership, fbid

👤 Profiles

username, fullName, biography, followerCount, isVerified, isPrivate, bioLinks, profileTags, profilePicUrl

Fields tied to a condition are null when that condition doesn't apply — replyToUsername is empty on a top-level post, quotedPostUrl on a post that quotes nothing. Nothing is guessed.

---

Three ways to pull data

Mode	What you give it	What you get
👤 Profile	usernames, @handles or profile URLs	The account's profile record + its posts, newest first, up to maxResultsPerQuery
🔍 Search	keywords	Posts matching the keyword (top and recent results)
💬 Post	post URLs	The post itself plus its replies, up to maxResultsPerQuery replies

Post mode returns only the thread you asked for — not the "related posts" Threads shows next to it. A post or account that does not exist (or is private) is reported in the run's status message and is never charged.

---

Who uses this, and for what

Who	What they run it for
👂 Social listening teams	Track brand, product or topic mentions as they happen
📊 Competitor analysts	Pull a rival's full posting history and see what actually gets engagement
📈 Trend researchers	Measure volume and tone around any keyword
🤝 Influencer marketers	Find who mentions and quotes whom, and spot paid partnerships
📰 Journalists & OSINT	Capture a whole reply thread with its conversation structure
🤖 AI & dataset builders	Collect labelled social text with engagement signals attached

---

Quick start — copy an input and run

One account's last 100 posts

{ "dataType": "profile", "usernames": ["zuck"], "maxResultsPerQuery": 100 }

Track a topic by keyword

{ "dataType": "search", "searchQueries": ["artificial intelligence"], "maxResultsPerQuery": 50 }

Several competitors at once (profile URLs work too)

{ "dataType": "profile", "usernames": ["https://www.threads.com/@nasa", "@natgeo"], "maxResultsPerQuery": 200 }

A post and its first 200 replies

{ "dataType": "post", "postUrls": ["https://www.threads.com/@zuck/post/DeZtp-TkQHh"], "maxResultsPerQuery": 200 }

---

How to use

1. Pick a Data type: profile, search or post.
2. Fill the matching field — usernames (with or without @, or the profile URL), search queries, or post URLs (threads.com or threads.net).
3. Set Max results — posts per profile or keyword, or replies per post.
4. Run. The status message tells you how many records each profile, keyword or post returned, and names any that were not found.

---

Output example

{
  "recordType": "post",
  "id": "4016607597105347552",
  "code": "De921QjmXvg",
  "url": "https://www.threads.com/@mosseri/post/De921QjmXvg",
  "text": "Really enjoyed my conversation with @ColinandSamir about our recent steps into longer-form…",
  "createdAt": "2026-10-26T17:49:19+00:00",
  "likeCount": 229,
  "replyCount": 50,
  "repostCount": 66,
  "quoteCount": 12,
  "mentions": ["colinandsamir"],
  "quotedPostUrl": "https://www.threads.com/@colinandsamir/post/De90Pbuk52l",
  "quotedPostAuthor": "colinandsamir",
  "replyToUsername": null,
  "authorUsername": "mosseri",
  "authorIsVerified": true,
  "detectedLanguage": "en",
  "isEdited": false
}

---

Performance

Measured runs:

Request	Records	Time
3 profiles × 50 posts	153	10–26 s
2 profiles × 200 posts	401	28–32 s
2 posts × 100 replies	202	9–14 s
1 keyword	21	~10 s
3 keywords	66–100	15–27 s

Keyword search returns what Threads shows a signed-out visitor for that keyword — typically 15 to 30 posts per keyword. Use several related keywords to widen coverage.

Pricing

Pay per result: $0.002 per record (post or profile) returned, plus $0.00005 per run start.

Records	Price
100	$0.20
1,000	$2.00

Accounts or posts that are not found are never charged. Set a maximum cost per run in the run options to cap spend.

FAQ

Do I need a Threads or Instagram account? No. The actor reads public Threads data — no login, no cookies, no API key.

How many posts can I get from a profile? As many as you set in Max results — the actor keeps going back through the profile's history. If an account has fewer posts than that, you get all of them.

Why does a keyword search return fewer posts than a profile? Threads shows signed-out visitors a limited set of results per keyword. Profiles and reply threads have no such limit.

Can I get posts from a private account? No. Private accounts are not public data and are not returned.

How do I find who a post is replying to? replyToUsername gives the account being answered, and rootPostUsername the author who started the thread. Both are null on top-level posts.

Are quoted posts separate rows? No — a quoted post is attached to the post that quotes it (quotedPostUrl, quotedPostAuthor, quotedPostText), so your counts are not inflated by other people's posts.

Keywords

threads scraper, threads api, threads posts scraper, meta threads data, threads search scraper, threads profile scraper, threads replies scraper, social media scraper, threads engagement data, social listening tool, threads mentions tracker

Related actors

• Reddit Thread Scraper
• StockTwits Scraper
• LinkedIn Jobs Scraper
• ESPN Sports Scraper

Disclaimer

This actor collects only publicly available post data from Threads and is not affiliated with Meta. You are responsible for how you use the data.

Changelog

Version	Date	Changes
1.2	2026-10-29	Profiles and reply threads now go as deep as Max results asks (hundreds of posts instead of the first ~15). Post mode returns only the requested thread — the "related posts" Threads shows beside it are no longer included, and a post that does not exist is reported instead of returning other posts. Quoted and reposted posts are attached to the post that shares them. Search adds recent results. Profile URLs and @handles accepted. More reliable runs, a per-query summary in the status message, and links on threads.com.
1.1	2026-08-18	Added 16 fields: @mentions, shared links with preview cards, reply-chain context (who a post answers and who started the thread), language detection, edit flag and media dimensions.
1.0	2026-07-14	Initial release — profile posts, search, and post threads with full engagement data