Threads Replies Scraper: Replies, Likes, Authors, No Login avatar

Threads Replies Scraper: Replies, Likes, Authors, No Login

Pricing

from $0.70 / 1,000 results

Go to Apify Store
Threads Replies Scraper: Replies, Likes, Authors, No Login

Threads Replies Scraper: Replies, Likes, Authors, No Login

Replies under public Threads posts: reply text, author, likes, replies, reposts, time and media. No login needed. $1 per 1,000 results, platform usage included.

Pricing

from $0.70 / 1,000 results

Rating

0.0

(0)

Developer

One Dollar Store

One Dollar Store

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Features

Limited permissions

Share

Threads Replies Scraper: replies under public Threads posts

$1 per 1,000 replies. Platform usage included. No rental, no minimum.

Paste links to public Threads posts. For each post you get the replies the logged out page shows, one row per reply: the reply text, the author, likes, replies, reposts, the time, pictures or GIFs, and which post and which reply it answers. No login, cookies or API key are needed.

Open it in Apify Console

New to Apify? [Create a free account](https://www.apify.com?fpr=ymnoit) (referral link).

How much does Threads Replies Scraper cost?

RepliesCost
1,000$1.00
10,000$10.00
100,000$100.00

One flat price, platform usage included, so there is no separate compute or proxy bill. You pay only for reply rows in the dataset.

A realistic example: reading 50 posts every day returns about 350 replies a run (our tests showed about 7 direct replies per post), so about $0.35 a run and about $10.50 a month.

How many replies does a post give?

Read this before you buy. A logged out Threads page does not show every reply. It shows the first batch and loads the rest only for logged in users. This actor does not log in, so the depth per post is fixed by that page.

In a test on 10 November 2026 with 119 public posts (90 of them had 30 or more replies on Threads), the page held:

  • Direct replies: 7 per post on average, most posts between 6 and 10, at most 11.
  • With replies to replies switched on: 10 per post on average, at most 23.
  • Which ones: in our tests mostly the earliest replies a post received, in time order, not the most liked.

The postReplyCount field on every row tells you how many replies the post has on Threads, so you can see how much of it you got. If you need thousands of replies under one post, this actor will not reach them. It suits many posts at a shallow depth: sampling reactions across a list of posts, tracking early replies, or checking who answers a brand account.

Why use it

  • Many posts, one run. Paste a list of post links. The run reads them a few at a time and stops at your row limit.
  • Replies to replies, if you want them. A switch adds the answers Threads shows next to a reply (for example the post author answering). Each carries a depth of 2 or more and the link to the reply it answers.
  • Signals other tools skip. likedByPostAuthor shows replies the author of the post liked, isByPostAuthor and isPinned show author replies and pinned replies, position keeps the order of the page.
  • Clean rows. Numbers are numbers, times are ISO 8601 UTC, and no reply appears twice in one run. Summaries and diagnostics are never billed.
  • No profile photos. Replies come from private people, so the rows carry usernames and display names as the page shows them, but no avatar links.

How to use Threads Replies Scraper

  1. Open the actor, paste one or more Threads post links, press Start.
  2. Or paste this input:
{
"postUrls": [
"https://www.threads.com/@nasa/post/Decc755lYhC",
"https://www.threads.com/@zuck/post/DfNR0zhEdWv"
],
"maxRepliesPerPost": 100,
"includeNested": false,
"maxItems": 50
}
  1. Download the results as JSON, CSV or Excel, or read them through the API.

To get a post link, open the post on Threads, press the share button and copy the link. Links on threads.com and threads.net both work, with or without the extra text after a question mark, and so do short links such as https://www.threads.com/t/Decc755lYhC.

Use it from code

curl -X POST "https://api.apify.com/v2/acts/one_dollar_store~threads-replies-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"postUrls": ["https://www.threads.com/@nasa/post/Decc755lYhC"], "maxItems": 50}'
from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("one_dollar_store/threads-replies-scraper").call(
run_input={"postUrls": ["https://www.threads.com/@nasa/post/Decc755lYhC"], "maxItems": 50}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item["authorUsername"], item["likeCount"], item["text"])

Use it from an AI assistant

Claude, ChatGPT, Cursor and other assistants can call this actor through Apify's MCP server. Add it with this server address:

https://mcp.apify.com?tools=one_dollar_store/threads-replies-scraper

Then ask, for example: "Read the replies under this Threads post https://www.threads.com/@nasa/post/Decc755lYhC and tell me what people are saying."

Switching from another Threads replies actor

Most Threads replies actors take post links and a cap per post. Here they are postUrls and maxRepliesPerPost, with includeNested for replies to replies. The core output fields are text, authorUsername, authorName, authorVerified, publishedAt, likeCount, replyCount, repostCount, url, postUrl and depth. Like the other actors that read the public page, this one returns the first batch of replies, not the full thread.

Input

FieldTypeDefaultWhat it does
postUrlslist of textrequiredLinks to public Threads posts, such as https://www.threads.com/@nasa/post/Decc755lYhC. Links that are not post links are skipped and named in the log. A post listed twice is read once.
maxRepliesPerPostnumber100Stop reading a post after this many replies (1 to 500). A logged out page holds about 7 to 10, so the page usually ends first.
includeNestedtrue or falsefalseAlso return the answers to replies that the page shows. They have depth 2 or more.
maxItemsnumber100The run stops after this many replies in total (minimum 10, maximum 10,000).
proxyConfigurationproxyDatacenterDatacenter proxy with a new address per request. After two blocked requests in a row it switches to residential for up to 10 requests. Pick the Residential group to use it from the start. Cost is included.

What data does Threads Replies Scraper return?

One row per reply, 41 fields. Empty fields are left out of a row.

  • Reply: replyId, code, url, text, publishedAt (UTC), isEdited, likeCount, replyCount, repostCount, quoteCount, language, depth (1 direct reply, 2 or more for answers in a chain), position (order on the page).
  • Media and links: mediaType (text, image, gif, video or carousel), imageUrls, videoUrls, altText, linkUrl, linkTitle, quotedPostUrl, hashtags, mentions.
  • Author: authorUsername, authorName, authorId, authorVerified.
  • Relation to the post: isByPostAuthor, replyToUsername, isReplyToPostAuthor, likedByPostAuthor, isPinned, parentId, parentUrl. For a direct reply the parent is the post. For depth 2 it is the reply above it.
  • The post: postId, postCode, postUrl, postAuthorUsername, postPublishedAt, postLikeCount, postReplyCount (all replies the post has on Threads).
  • Run: scrapedAt.

Like counts and reply counts are the numbers on the page when it was read.

Sample results

Real rows from a test run on 10 November 2026, shortened to the main fields. The rows are replies under public posts by the nasa and zuck accounts.

[
{
"url": "https://www.threads.com/@lisasigrest/post/Decc_2tGKLh",
"depth": 1,
"postUrl": "https://www.threads.com/@nasa/post/Decc755lYhC",
"authorUsername": "lisasigrest",
"authorName": "Lisa Sigrest",
"authorVerified": false,
"isByPostAuthor": false,
"likedByPostAuthor": true,
"text": "Wow 😍🙏😊✨️",
"publishedAt": "2026-10-13T18:28:38.000Z",
"likeCount": 10,
"replyCount": 0,
"repostCount": 0,
"mediaType": "text"
},
{
"url": "https://www.threads.com/@peewanseb/post/DecdIh5j7O4",
"depth": 1,
"postUrl": "https://www.threads.com/@nasa/post/Decc755lYhC",
"authorUsername": "peewanseb",
"authorName": "m (s/h) 🩷💜💙✌🏼",
"authorVerified": false,
"isByPostAuthor": false,
"likedByPostAuthor": true,
"text": "How it feels to be a nasa fan",
"publishedAt": "2026-10-13T18:29:49.000Z",
"likeCount": 89,
"replyCount": 0,
"repostCount": 0,
"mediaType": "gif",
"language": "en"
},
{
"url": "https://www.threads.com/@mrkampmann_ac/post/DeceHi_Gpnh",
"depth": 1,
"postUrl": "https://www.threads.com/@nasa/post/Decc755lYhC",
"authorUsername": "mrkampmann_ac",
"authorName": "David Kampmann",
"authorVerified": false,
"isByPostAuthor": false,
"likedByPostAuthor": false,
"text": "I assumed space x exploded again.",
"publishedAt": "2026-10-13T18:38:26.000Z",
"likeCount": 37,
"replyCount": 0,
"repostCount": 0,
"mediaType": "text",
"language": "en"
}
]

Limits

  • Depth. A logged out Threads page shows the first batch of replies under a post: about 7 direct replies on average in our test, at most 11, and a few more with replies to replies. postReplyCount shows how many the post has in all. The rest load only for logged in users, and this actor does not log in. For a keyword or hashtag view of Threads instead, use the Threads Search Scraper or the Threads Hashtag Scraper.
  • Which replies. The page chooses them, not you. In our tests they were mostly the earliest replies, in time order. They can change between runs as the post gets new replies.
  • Missing posts. A link to a post that was removed, belongs to a private account or never existed gives no rows. The run log names it. About 1 in 12 of the older post links in our test returned no post.
  • Hidden replies. Replies from private accounts, replies the author hid and replies Threads marks as unavailable are not on the page, so a post can show fewer replies than its count.
  • Only posts. Profile links and search links are not accepted. Use the Threads Profile Scraper to list a profile's posts first, then paste the post links here.
  • Not available without a login: replies beyond the first batch, a reply's own thread beyond what the page shows, private profiles and anything behind a login.
  • Threads' robots.txt asks automated clients not to crawl the site. This actor reads only public pages, as a logged out visitor, at a modest rate (three pages at a time, at least one second between page starts, each from a new proxy address). You decide for yourself how to use the data.
  • One run delivers at most 10,000 replies and lasts up to 60 minutes by default. In our tests a run read one post every 1.5 to 5 seconds, depending on how fast Threads answered.
  • A run ends early, and says so in its status line, when several posts in a row cannot be read, or when it is about to reach its time limit. You are charged only for the replies delivered.

FAQ

How much does it cost to scrape 10,000 Threads replies? $10. At about 7 direct replies per post (about 10 with replies to replies) that is roughly 1,000 to 1,400 posts.

Do I pay for compute or proxy on top? No. Platform usage, including the proxy, is included in the $1 per 1,000 price.

Can it get all the replies under a viral post? No. A logged out page shows only the first batch, so a post with 600 replies gives about 10 rows. The postReplyCount field tells you how many replies the post has on Threads.

Do I need a Threads or Instagram account? No. The actor only reads public pages that anyone can open without logging in.

Does it return personal data? Replies are written by private people. A row carries what the page shows publicly: username, display name, the text and the numbers. It has no profile photos, follower lists or contact details. You are responsible for lawful use of the data, for example under GDPR and e-mail marketing rules.

What if Threads refuses a request? It tries again from a new proxy address, up to three times. After two blocked requests in a row it switches from the datacenter to the residential proxy for up to 10 requests. If several posts in a row fail, the run stops early and says so in the log.

Is it legal? The actor collects only public data that Threads shows to any visitor. Threads' robots.txt asks automated clients not to crawl the site; this actor reads public pages as a logged out visitor at a modest rate, and you decide for yourself how to use the data. Follow the Threads terms of use and the data protection laws that apply to you, such as GDPR or CCPA, especially when you store or process personal data.

Is this an official Threads product? No. It is an independent tool and is not affiliated with or endorsed by Meta or Threads.

Do I need an Apify account? Yes. Actors run from an Apify account, and a free account is enough to start: it includes $5 of platform usage every month. You can sign up here. This is a referral link and it costs you nothing.

Feedback and support

Found a problem or want a field added? Open an issue on the Issues tab of this actor and it gets read. If the actor saved you time, an honest rating on the Reviews tab helps other people find it.

More from The One Dollar Store

Every actor here costs $1 per 1,000 results, platform usage included. See the whole store: https://apify.com/one_dollar_store

Social media

Changelog

  • 10 November 2026: clearer description and headings, field details for AI tools. Price and output unchanged.
  • November 2026: first release.