Threads Replies Scraper - Comments & Reply Threads, No Login avatar

Threads Replies Scraper - Comments & Reply Threads, No Login

Pricing

from $1.50 / 1,000 results

Go to Apify Store
Threads Replies Scraper - Comments & Reply Threads, No Login

Threads Replies Scraper - Comments & Reply Threads, No Login

Scrape replies (comments) under any Threads post without login: text, author, likes, date, whole nested reply threads and which replies the author liked. Top or newest first, about the first 900 per post. Or every reply an account wrote. From $1.50 per 1,000.

Pricing

from $1.50 / 1,000 results

Rating

5.0

(1)

Developer

Alom Dev

Alom Dev

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

a day ago

Last modified

Share

Threads Replies Scraper: Comments & Reply Threads, No Login

Get the replies (comments) under any Threads post as a table: paste post URLs and you get one row per reply with the text, author, likes, reply count, date, media and links, the reply it answers, and whether the post author liked it. You can also paste usernames to get every reply an account wrote.

  • No login needed. It reads what a logged-out visitor of threads.com sees. No account of yours is involved.
  • Whole reply threads. Threads shows only one answer under a reply. This Actor opens each thread and reads it in full, every row linked to the reply it answers (parentPostId). Or turn threads off to get only direct replies.
  • Top or newest first. Newest first follows a post as the reactions come in.
  • Only new replies on a schedule. Monitoring mode skips replies an earlier run returned, and you don't pay for them.
  • You pay for replies only. The post itself is not a row unless you ask for it.
  • Export to CSV, Excel or JSON, or pull results through the Apify API.

This Actor is a focused version of the Threads Scraper (same code, same prices). Use the Threads Scraper if you also need a profile's posts, reposts or a keyword search.

What can you use it for?

  • Reactions to an announcement: read what people answer under a launch post, a statement or an ad.
  • Customer feedback: collect the replies under your own posts and sort them by likes.
  • Community research: see what an account says in conversations, which is often more telling than its posts.
  • Datasets for analysis and AI: real reply threads with timestamps, authors and engagement counts.

Input

FieldWhat it does
postUrlsThreads post URLs, e.g. https://www.threads.com/@mosseri/post/DdUI1VfG_42 (threads.net works too).
usernamesOptional. For each account: the replies it wrote (its Replies tab), each with the post it answered.
maxRepliesMax replies per post and per account. Default 100.
repliesSorttop (Threads' order) or recent (newest first). Left empty: top, or newest first when monitoring is on.
includeNestedRepliesThe whole thread under each reply. Default on. Off = only direct replies to the post.
maxNestedRepliesMax replies under one reply. Default 20, so one busy thread cannot use up maxReplies.
includeOriginalPostAlso return the post itself as a row. Default off.
postedAfterOnly replies after a date, e.g. 2026-10-01 or 7 days.
minLikesKeep only replies with at least this many likes.
includeViewsFill viewCount (the number Threads shows under a reply, e.g. "2.2K views") on every reply. One extra request per reply, about 1.5 s each, not charged. Default off.
onlyNewSinceLastRun + monitorNameSkip replies an earlier run with the same monitor name returned.
{ "postUrls": ["https://www.threads.com/@mosseri/post/DdUI1VfG_42"], "maxReplies": 300, "repliesSort": "top" }
{ "usernames": ["mosseri"], "maxReplies": 50 }
{ "postUrls": ["https://www.threads.com/@mosseri/post/DdUI1VfG_42"], "onlyNewSinceLastRun": true, "monitorName": "launch-post" }

Switching from another Threads replies scraper?

Keep your input. These field names are accepted as they are: post_urls or postUrls (strings or { "url": ... } objects), max_replies / maxRepliesPerPost, include_nested_replies / includeNestedReplies / includeChildReplies, and sortOrder (top or recent). No session id or cookie is needed.

Output example

{
"type": "reply",
"postId": "3731234567890123456",
"code": "Dd1Pxa2ExAm",
"url": "https://www.threads.com/@example_user/post/Dd1Pxa2ExAm",
"text": "This is the part I was waiting for. When does it roll out in Europe?",
"username": "example_user",
"fullName": "Example User",
"isVerified": false,
"likeCount": 214,
"replyCount": 3,
"repostCount": 1,
"quoteCount": 0,
"mediaType": "text",
"media": [],
"isReply": true,
"replyToUsername": "zuck",
"parentPostId": "3730000000000000001",
"rootPostId": "3730000000000000001",
"isLikedByAuthor": true,
"date": "2026-09-28T15:04:11.000Z",
"source": "post:Dd1MqfcG0aH",
"scrapedAt": "2026-10-12T09:00:00.000Z"
}

(The reply above is made up; the fields are what you get.) rootPostId is the post whose replies you asked for. parentPostId is the row this reply answers: the post itself for a direct reply, another reply inside a thread. Rows from usernames also carry repliedToPost (the post that was answered) and sourceTab: "replies". Values Threads doesn't show are null, never a made-up 0.

How much does it cost?

The same prices as the Threads Scraper: from $1.50 per 1,000 replies, plus $0.005 per run. One result = one reply row. Platform usage (compute, proxy) is included.

Apify planPrice per 1,000 replies
Free$2.50
Starter (Bronze)$2.00
Scale (Silver)$1.75
Business (Gold) and above$1.50

500 replies under a post cost $1.25 on the Free plan and $0.75 on Business. You pay only for rows you receive: replies a monitor already returned, replies outside your date window and posts that don't exist are free.

Monitoring (only new replies)

Turn on "Only new replies since my last run", give it a name (e.g. launch-post) and schedule the run in Apify Console. Each run reads the replies newest first and stops at the first one an earlier run delivered, so an hourly check of a quiet post costs almost nothing.

Limitations

  • Roughly the first 1,000 direct replies per post. That is how far Threads lets a logged-out visitor page: a post with about 6,600 replies gave 908 direct replies in our test.
  • Threads are read up to 6 levels deep and up to maxNestedReplies rows per direct reply (default 20). In our test a post gave 245 direct replies and 79 replies inside threads, and 32 of its 34 threads were complete.
  • A reply's counter can be slightly higher than the rows you get. Some replies are not shown to logged-out visitors (in the same test, 64 of 66 counted replies came back).
  • Speed: about 250 replies a minute.
  • Monitoring follows new direct replies. Threads under replies an earlier run already delivered are not read again.
  • No view counts. Threads doesn't show them to logged-out visitors.
  • A post URL that doesn't exist fails that input only (it is named in the run's status message); the rest of the run is delivered.

FAQ

Do I need a Threads or Instagram account? No. Nothing is logged in, so there is nothing to ban.

Is "replies" the same as "comments"? Yes. Threads calls the comments under a post replies.

Can I get the replies to a reply? Yes, whole threads are included by default. Each row's parentPostId tells you which reply it answers. isLikedByAuthor marks the replies the post's author liked.

Is it legal? The Actor collects only what Threads shows publicly without login. Replies are personal data: check that your use has a lawful basis (GDPR and similar laws) before you store or process them.

More scrapers from the same developer

Feedback

Missing a field, found a bug, or need a feature? Open an issue in the Issues tab and I'll take a look. If this Actor saved you time, a short review on the Store page helps other people find it.