Threads Replies & Comments Scraper avatar

Threads Replies & Comments Scraper

Pricing

from $0.16 / 1,000 reply extracteds

Go to Apify Store
Threads Replies & Comments Scraper

Threads Replies & Comments Scraper

Export public replies and comments from Threads posts: author, text, likes, reply counts, media and nesting. Loads every reply page, up to 1,000 per post. About $0.30 per 1,000 replies. No login.

Pricing

from $0.16 / 1,000 reply extracteds

Rating

0.0

(0)

Developer

Automation Lab

Automation Lab

Maintained by Community

Actor stats

1

Bookmarked

370

Total users

104

Monthly active users

0.14 hours

Issues response

a day ago

Last modified

Categories

Features

Limited permissions

Share

Threads Replies Scraper

Extract public replies and comments from Threads post URLs.

Use this Apify Actor when you need structured reply data for a specific Threads conversation, launch announcement, creator post, brand mention, or community discussion.

The Actor is designed for public Threads content. It starts with an HTTP-first strategy to keep runs lightweight and affordable.


What does Threads Replies Scraper do?

Threads Replies Scraper reads public Threads post pages and saves reply/comment records to an Apify dataset.

It is focused on the conversation below a post, not on profile discovery or keyword search.

Typical use cases include:

  • 💬 Monitoring replies to brand announcements
  • 📣 Tracking launch feedback below a creator post
  • 🧪 Collecting comment samples for sentiment analysis
  • 🧑‍🤝‍🧑 Reviewing community engagement around public posts
  • 📊 Exporting Threads replies to CSV, JSON, Excel, Google Sheets, or your own database

Who is it for?

This Actor is useful for teams and individuals who already know which Threads posts they want to analyze.

Social media managers

Track replies to campaign posts and identify questions, complaints, and high-value audience feedback.

Brand monitoring teams

Collect public comments from posts that mention your company, product, executives, or competitors.

Creator economy researchers

Analyze how audiences respond to creator content, launch posts, and collaborations.

Community managers

Export conversations for moderation review, issue triage, or recurring community reports.

Data teams

Feed Threads conversation data into downstream NLP, sentiment, BI, or warehouse pipelines.


Why use this Actor?

Threads conversations can move quickly. Manual copy-paste does not scale when you need repeatable exports.

This Actor gives you:

  • 🧵 Post-specific reply extraction
  • 👤 Author profile fields
  • ✅ Verified badge detection when present
  • ❤️ Engagement counts when present
  • 🖼️ Media URL collection when present
  • 🪜 Nested reply metadata when present
  • 🧾 Clean dataset rows for analysis

What data can you extract?

Each dataset row represents one Threads reply/comment.

FieldDescription
postUrlSource Threads post URL you submitted
replyIdInternal reply/post ID when available
replyUrlPublic URL for the reply when username and code are available
parentPostIdParent post/reply ID when exposed by Threads
authorUsernameThreads username
authorDisplayNameAuthor display name
authorProfileUrlPublic Threads profile URL
authorVerifiedWhether the author is verified, when available
textReply text
createdAtReply timestamp in ISO format when available
likeCountLike count when available
replyCountReply count when available
repostCountRepost count when available
quoteCountQuote count when available
mediaUrlsOne representative URL per attached image or video, in payload order
quotedPostQuote/share metadata when present
depthInternal payload depth, useful for debugging nested data
threadLevelReply nesting level when Threads exposes it
scrapedAtTimestamp when the row was saved

How much does it cost to scrape Threads replies?

The Actor uses pay-per-event pricing.

You pay a small start event and then a per-reply event for saved dataset rows.

Current BRONZE reference pricing is $0.005 per run start plus about $0.00026162 per extracted reply (about $0.26 per 1,000 replies). Higher/lower Apify plan tiers may see different per-reply rates on the Store page before running. A run that fails, or finds no post it can read, saves nothing and costs nothing.

From 2026-12-05 the per-reply price will be $0.002 on FREE and BRONZE (about $2 per 1,000 replies), $0.0018 on SILVER and $0.0016 on GOLD and higher plans. The $0.005 start fee stays the same.

For testing, start with one post URL and a low maxRepliesPerPost value.


How to use Threads Replies Scraper

  1. Open the Actor on Apify.
  2. Paste one or more public Threads post URLs into postUrls.
  3. Set maxRepliesPerPost to the number of replies you need per post.
  4. Keep includeNestedReplies enabled if you want replies-to-replies when available.
  5. Run the Actor. The default 30-minute timeout supports large batches; you can still choose a longer timeout in run settings for unusually slow inputs.
  6. Download the dataset as JSON, CSV, Excel, XML, or RSS.

Input

The main input is postUrls.

{
"postUrls": [
{ "url": "https://www.threads.com/@nasa/post/DZceA72Drjf" }
],
"maxRepliesPerPost": 100,
"includeNestedReplies": true,
"proxyConfiguration": {
"useApifyProxy": true
}
}

Input fields

postUrls

Public Threads post or share URLs to scrape.

Supported formats:

https://www.threads.com/@username/post/POST_CODE
https://www.threads.com/share/SHARE_CODE

Share links are resolved to their public post before extraction. threads.net URLs are normalized to threads.com.

maxRepliesPerPost

Maximum replies saved per submitted post URL, up to 1,000. The Actor loads further pages of replies the way the Threads website does, so a popular post returns as many replies as you ask for, as long as Threads shows them to logged-out visitors.

Use a small number for first tests.

includeNestedReplies

When enabled, the Actor keeps nested replies if Threads includes them in the public payload.

proxyConfiguration

Proxy settings.

Apify Proxy with the Residential group is enabled by default as a fallback because Threads can return incomplete public payloads from some cloud datacenter IPs. The Actor first tries the direct route, then automatically uses the default Residential route only when needed. Custom proxy configurations are honored from the first request.


Output example

{
"postUrl": "https://www.threads.com/@example/post/POST_CODE",
"replyId": "1234567890",
"replyUrl": "https://www.threads.com/@reply_author/post/REPLY_CODE",
"parentPostId": "9876543210",
"authorUsername": "reply_author",
"authorDisplayName": "Reply Author",
"authorProfileUrl": "https://www.threads.com/@reply_author",
"authorVerified": false,
"text": "This is a public reply.",
"createdAt": "2026-06-14T10:00:00.000Z",
"likeCount": 12,
"replyCount": 1,
"repostCount": 0,
"quoteCount": 0,
"mediaUrls": [],
"quotedPost": null,
"depth": 14,
"threadLevel": 1,
"scrapedAt": "2026-06-14T10:05:00.000Z"
}

Tips for best results

  • Use direct post URLs, not profile URLs.
  • Keep first runs small while validating output.
  • Public posts with no replies may produce no rows.
  • Deleted, private, unavailable, or invalid posts are skipped.
  • Keep the default Apify Proxy setting enabled for reliable cloud runs.
  • Large batches fetch up to four posts concurrently and checkpoint every completed batch. If a run times out or restarts, resurrecting it continues with the remaining posts while keeping already saved results.
  • Run the Actor regularly for recurring monitoring.

Limitations

Threads is a Meta property and can change its public page structure.

The Actor reads the public post page and then loads further reply pages the same way the website does for a logged-out visitor. Threads decides which replies a logged-out visitor sees; a few hidden or restricted replies may be missing compared with the logged-in app.

The final status message says how many replies were saved against your limit and, for a post that returned fewer, why (for example "Got 40 of 100 for post CODE: Threads shows no more replies to a logged-out visitor").

Private content, account-only content, and login-gated content are not supported.


Diagnostic reporting

Failed operations send sanitized diagnostic input, exceptions, and Actor/build/run IDs to our private GlitchTip service for repair. Secret fields and URL query strings are removed; reports are retained for 30 days. Diagnostic reporting does not change dataset output or charging.


Integrations

You can connect the dataset to:

  • Google Sheets for social reporting
  • Slack alerts for high-priority replies
  • Airtable for community triage
  • BigQuery or Snowflake for analytics
  • OpenAI or Claude workflows for sentiment analysis
  • Zapier or Make for no-code automation
  • Apify webhooks for run-finished automation

API usage

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/threads-replies-scraper').call({
postUrls: [{ url: 'https://www.threads.com/@nasa/post/DZceA72Drjf' }],
maxRepliesPerPost: 50,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/threads-replies-scraper').call(run_input={
'postUrls': [{'url': 'https://www.threads.com/@nasa/post/DZceA72Drjf'}],
'maxRepliesPerPost': 50,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~threads-replies-scraper/runs?token=$APIFY_TOKEN" \
-H 'Content-Type: application/json' \
-d '{
"postUrls": [{"url": "https://www.threads.com/@nasa/post/DZceA72Drjf"}],
"maxRepliesPerPost": 50
}'

MCP usage

Use this Actor from Apify MCP tools in Claude Desktop or Claude Code.

MCP URL:

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

Claude Code setup

$claude mcp add --transport http apify-threads-replies "https://mcp.apify.com/?tools=automation-lab/threads-replies-scraper"

Claude Desktop setup

Add this to your Claude Desktop MCP configuration:

{
"mcpServers": {
"apify-threads-replies": {
"url": "https://mcp.apify.com/?tools=automation-lab/threads-replies-scraper"
}
}
}

Cursor setup

Add the same mcpServers entry to .cursor/mcp.json in your project or to Cursor's global MCP settings.

VS Code setup

Add an HTTP server named apify-threads-replies with the MCP URL above in .vscode/mcp.json, then start it from the MCP servers view.

Example prompts:

  • "Scrape replies from this Threads post and summarize the top complaints."
  • "Export public comments from these Threads posts and group them by sentiment."
  • "Find verified users replying to this launch announcement."

FAQ

Can I scrape private Threads replies?

No. This Actor supports anonymously accessible public replies only. It does not log in, bypass source restrictions, or collect private account-only content. A public-looking URL may still be actively restricted by Threads for certain audiences.

Why did a public post return fewer replies than I see in the app?

The Actor pages through all replies Threads shows to a logged-out visitor, up to your maxRepliesPerPost. The logged-in app can show some replies that Threads hides from logged-out visitors, and the reply count on a post also counts deleted and hidden replies. The run's status message names any post that came back short and why.

Can I schedule recurring monitoring?

Yes. Use Apify schedules with the same postUrls input and export each run's dataset to your reporting workflow.


Data handling, AI, and dependencies

The Actor uses deterministic HTTP requests and parsing; it does not call an AI model or send data to an AI provider. Submitted public URLs are requested from Threads directly and, when needed, through the configured Apify Proxy. Public reply and author fields are written only to the run's Apify dataset. Large-batch progress stores hashed post identifiers in the run key-value store, not submitted URLs.

The Actor maintains no external database or cache. Datasets, key-value stores, and logs follow your Apify account retention settings and can be deleted with Apify's run and storage controls. Logs can contain submitted public post URLs, so choose retention settings appropriate for your use case.

Threads is named only to identify the public data source. This Actor is independently operated and is not affiliated with or endorsed by Meta or Threads.


Legality and ethics

This Actor is intended for public Threads content only.

Do not use it to collect private, login-only, or restricted information.

Always follow applicable laws, platform terms, and privacy obligations in your jurisdiction.

If you process personal data, make sure you have a valid legal basis and retention policy.


Troubleshooting

The Actor returned no rows

Check that you submitted a post URL or an official /share/ link, not a profile URL. The post may also have no public replies or may be unavailable. The run's status message says which: for example "Got 0 replies: the post is not available to logged-out visitors (1 deleted or unavailable). No charge."

When no submitted link opens a post a logged-out visitor can read (every link is deleted, restricted, private, an expired share link or not a post URL), the run ends SUCCEEDED with an empty dataset and no charge. API and scheduled callers can read the reason from the run's status message and from the RUN_DIAGNOSTIC record in the run's default key-value store: reason is invalid_input (no link resolved to a post) or target_unavailable (posts are deleted or restricted), with counts. Check RUN_DIAGNOSTIC or the item count rather than only the run status if a schedule keeps returning nothing.

Threads returned an invalid post page

The URL may be deleted, typoed, private, or regionally unavailable. Open it in a browser without logging in to confirm it is public.

Threads actively restricts this content for anonymous access

This means the final response mounted Threads' restricted-content page, not a verified post with zero replies. Restricted content is not supported; proxies or a longer timeout are not a promised remedy. The restriction can have different audience/access causes; the Actor does not infer a legal cause from this marker alone.

Restricted and deleted posts are skipped and named in the final status message; no diagnostic rows are inserted. In a mixed batch, useful replies remain in the dataset and are charged as usual. A run where every post is restricted or deleted ends SUCCEEDED, empty and free (see "The Actor returned no rows"). A post whose reply count is positive but whose replies Threads shows to no logged-out visitor completes like a zero-reply post. A run fails only when a post could not be read at all after retrying (unknown page or network failure) and no replies were saved.

Should I enable proxies?

Keep the default Apify Proxy / Residential fallback enabled for reliability. It is used only when the direct route does not expose replies. Each post uses at most one fresh fallback attempt, avoiding repeated transfer and delay when a public post has no visible replies. If you override proxy settings and receive empty output, restore the default proxy configuration before retrying.

What should I do if a large batch times out?

The Actor defaults to a 30-minute timeout and checkpoints each completed post. Resurrect the timed-out run with a longer timeout: it will keep existing dataset rows and continue with the remaining posts rather than restarting the whole batch. For very large batches, you can also split the URL list into smaller runs.


These automation-lab Actors may be useful with this workflow:


Changelog

2026-11-21

  • Empty pages from Threads (a page with no post data) are retried on fresh connections like rate limits, so these posts return replies instead of failing the run.

2026-11-20

  • Rate limits ("too many requests") and Threads server errors are retried after a short pause on fresh connections, so these runs return replies instead of failing.
  • The status message names submitted links that do not open a post, even when other posts returned replies.

2026-11-19

  • A run where every post is deleted, restricted by Threads, or not a valid post link now ends successfully with no rows and no charge, and its status message and RUN_DIAGNOSTIC record say why (it failed before).
  • A post that shows a reply count but no replies to logged-out visitors is reported as such instead of failing the run.

2026-11-17

  • Loads all reply pages, not only the first ~15 replies on the post page: a limit of 100 or 1,000 now returns that many when the post has them.
  • includeNestedReplies: false now returns the post's direct replies (it returned none before).
  • Failed runs are no longer charged the start fee; replies are charged before they are saved.
  • The final status message says how many replies were saved against the limit and why a post came back short.

0.1

Initial version focused on public Threads post reply extraction from embedded page payloads.