Threads Replies Scraper

Export public Threads replies from post links or a profile's recent posts. Download reply text, authors, available engagement and media as JSON, CSV or Excel.

Public subset, not a complete conversation: Threads may show logged-out visitors only some replies. Profile input collects replies to that profile's posts, not a history of replies written by the account. No Threads login or cookies are required.

Quick start

1. Paste one public post into postUrls and start with a small maxRepliesPerThread.
2. Run the Actor, then open its dataset to review or export the saved replies.
3. Check the OUTPUT summary for coverage and any skipped or empty targets. Choose your connection preference in the input form.

{
  "postUrls": [{ "url": "https://www.threads.com/@nasa/post/DbTnB4JGWEX" }],
  "maxRepliesPerThread": 5,
  "maxDepth": 3
}

Canonical /@username/post/CODE, /share/TOKEN, /t/CODE and /post/CODE links are accepted, including threads.net aliases, tracking parameters and trailing slashes. Short links must resolve to a valid Threads post.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a small preconfigured starting point. Review the target and limits before running.

• Export replies from a Threads post — Collect up to 20 public replies beneath one post.
• Monitor recent replies to a Threads post — Collect up to 40 replies after a fixed timestamp. Update changedSince for your own monitoring window. This example does not schedule itself.
• Collect reply conversations from a Threads profile — Discover up to five visible profile posts and collect up to 10 replies per post, rather than the account's authored-reply history.

What you get

• Reply text, URL, ID, timestamp, mentions, hashtags, and external links
• Reply author username, profile URL, avatar, display name, ID, and verification when publicly visible
• Likes, replies, reposts, quotes, and shares when Threads exposes them
• Media URLs, type, dimensions, audio and accessibility metadata when available
• Root-post URL, author, text, engagement, and stable provenance
• Parent reply ID, parent author, and depth when publicly evidenced
• Monitoring and quality fields such as changedSinceMatched, scrapedAt, and warning

Who is it for?

• Social-listening researchers reviewing exposed reactions to known public posts.
• Creator and community teams sampling responses beneath selected account posts.
• Conversation analysts retaining evidenced parent relationships without reconstructing a complete tree.
• Data developers joining reply, root-post and source context in their own analysis.

How you can use the data

• Review the existing NASA post's visible replies. Use the Quick start link with five replies and a depth limit of three. Keep replyUrl, text, rootPostUrl and available author attribution rather than claiming every reply shown in a platform total.
• Sample responses beneath profile posts. Use the existing NASA profile recipe with a small per-thread cap. Profile input discovers up to five visible posts and collects replies to them, not replies authored by NASA across other conversations.
• Review recent publications with unknown dates separated. Apply the existing first-of-October cutoff to the known post and retain createdAt and changedSinceMatched. Undated replies remain eligible, and the cutoff does not detect edits or remember earlier exports.
• Join only evidenced conversation edges. Keep root and parent identifiers with depth when available. Null parentage stays unknown rather than being guessed into a thread tree. Perform topic grouping, recurring comparisons or scheduled notifications in your own workflow and inspect OUTPUT coverage first.

Input settings

Setting / API key	Type	Description
Post URLs — postUrls	array	Public Threads canonical post URLs, /share/TOKEN, /t/CODE, or /post/CODE links. Domain aliases, tracking parameters and trailing slashes are supported.
Profile URLs — profileUrls	array	Public profile URLs. The Actor discovers visible posts and collects their replies.
Reply limit — maxRepliesPerThread	integer	Maximum replies saved per thread (1–1000).
Depth limit — maxDepth	integer	Maximum evidenced conversation depth (1–10). Unknown parent chains have depth: null and remain eligible.
Publication cutoff — changedSince	string	Optional ISO date-time. Save replies at or after this timestamp. Replies with an unknown publication time remain eligible, so review createdAt before treating results as strictly new.
Connection mode — connectionMode	string	automatic tries direct first and may use one paid Apify Proxy fallback. direct never uses a proxy. Find this choice under Advanced.

Provide at least one post or profile URL, with at most 100 combined targets. Each profile covers up to five visible posts. Collection stops after 4½ minutes. Check OUTPUT for any remaining targets.

Input recipes

Bounded post export:

{
  "postUrls": [{ "url": "https://www.threads.com/@nasa/post/DbTnB4JGWEX" }],
  "profileUrls": [],
  "maxRepliesPerThread": 20,
  "maxDepth": 3
}

Recent replies: add an ISO timestamp to a bounded post input. This filters reply publication times. It does not detect edits or remember previous runs.

{
  "postUrls": [{ "url": "https://www.threads.com/@nasa/post/DbTnB4JGWEX" }],
  "maxRepliesPerThread": 10,
  "changedSince": "2026-10-01T00:00:00.000Z"
}

Replies beneath profile posts:

{
  "profileUrls": ["https://www.threads.com/@nasa"],
  "maxRepliesPerThread": 5,
  "maxDepth": 2
}

Output data

Data	Key fields
Reply	replyUrl, text, createdAt, mentions, hashtags
Author	authorUsername, authorProfileUrl, authorDisplayName, authorVerified
Engagement	likeCount, replyCount, repostCount, quoteCount, shareCount
Conversation	rootPostUrl, rootText, parentReplyId, parentAuthorUsername, depth
Media	mediaType, mediaUrls, accessibilityCaption, quotedPostUrl, repostedPostUrl
Coverage	sourceUrl, isPublicSubset, warning, changedSinceMatched, scrapedAt

These are the main fields. The dataset schema lists the complete export. Unavailable values are null, and empty lists are []. Unknown parentage remains depth: null. The Actor does not guess a conversation tree. Media and quote details appear only when Threads exposes them.

Example record

Illustrative field subset, not an observed reply or a promise that optional fields are populated:

{
  "sourceType": "post",
  "sourceUrl": "https://www.threads.com/@nasa/post/DbTnB4JGWEX",
  "rootPostId": "DbTnB4JGWEX",
  "rootPostUrl": "https://www.threads.com/@nasa/post/DbTnB4JGWEX",
  "rootAuthorUsername": "nasa",
  "replyId": "exampleReplyCode",
  "replyUrl": "https://www.threads.com/@example/post/exampleReplyCode",
  "parentReplyId": null,
  "depth": null,
  "authorUsername": "example",
  "authorProfileUrl": "https://www.threads.com/@example",
  "text": "A public reply",
  "mentions": [],
  "hashtags": [],
  "externalUrls": [],
  "likeCount": null,
  "mediaUrls": [],
  "changedSinceMatched": true,
  "scrapedAt": "2026-08-06T12:00:00.000Z",
  "isPublicSubset": true,
  "warning": "Threads may expose only a public subset; unavailable metadata and unevidenced depth are null. maxDepth filters only evidenced parent chains."
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The Actor uses pay-per-event pricing. One start event is charged per run, including a run that finds no replies.

One reply event is charged for each successfully saved reply row. Coverage summaries and empty or error diagnostics are not paid dataset rows.

See the live Pricing tab for current rates and discounts.

Tips for best results

• Start with one post. Use a small reply limit before collecting several conversations.
• Use stable post links. Active threads can change between runs, so compare exports in your own workflow.
• Review the coverage summary. Check OUTPUT for saved counts and empty, unavailable or failed targets before drawing conclusions.
• Treat the cutoff as a publication filter. changedSince does not detect edits or remember prior runs. Review unknown timestamps separately.
• Set a bounded reply limit. Profile inputs can cover several posts, so the limit applies separately to each discovered thread.

Limits and caveats

• Public subset only. Threads decides which replies logged-out visitors can see. The export may be smaller than the displayed total.
• No access bypass. Private, removed, restricted or login-only content is not bypassed. Inaccessibility alone does not identify which restriction applies.
• Missing metadata stays unknown. Author and engagement details can be absent. Unknown parentage stays depth: null, and unknown publication times remain eligible when a cutoff is supplied.
• Bounded collection. Each profile covers up to five visible posts. Collection stops after 4½ minutes. The OUTPUT summary shows coverage and remaining targets.
• Partial and empty results. Useful replies from other targets are preserved when safe. Completed collection with no usable replies succeeds with an empty dataset and a truthful reason. Unexpected extraction failures remain visible. Fatal configuration, billing and essential storage errors fail the run.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~threads-replies-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"postUrls":[{"url":"https://www.threads.com/@nasa/post/DbTnB4JGWEX"}],"maxRepliesPerThread":20}'

Node.js

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

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/threads-replies-scraper').call(run_input={
    'postUrls': [{'url': 'https://www.threads.com/@nasa/post/DbTnB4JGWEX'}],
    'maxRepliesPerThread': 20,
})
items = client.dataset(run['defaultDatasetId']).list_items().items

MCP and AI agents

You can ask your AI assistant to collect data with Threads Replies Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Threads Replies Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

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

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Threads Replies Scraper by Fetch Cat, or give it the identifier fetch_cat/threads-replies-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Threads Replies Scraper to collect up to 5 public replies beneath https://www.threads.com/@nasa/post/DbTnB4JGWEX with a depth limit of 3 and direct mode. Keep root links and unknown parentage without claiming the complete conversation.”
• “Collect replies beneath the visible recent posts of https://www.threads.com/@nasa with up to 2 replies per thread, depth limit 2 and direct mode. Group by root post without calling this the account's authored-reply history.”
• “Retrieve up to 5 replies beneath https://www.threads.com/@nasa/post/DbTnB4JGWEX with a publication cutoff of 1 October 2026 at midnight UTC and direct mode. Keep unknown timestamps separate rather than describing them as definitely new.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

What data can I export with Threads Replies Scraper?

You can scrape Threads replies with author, content, engagement, media, root-post, parent-edge, monitoring, and provenance fields documented above.

Can it collect every reply on Threads?

It collects replies available on public logged-out Threads surfaces, up to your requested limit. Threads may expose only a subset.

Does it require a Threads login?

No. The Actor is designed for public data and does not accept account cookies or credentials.

Can I monitor only new replies?

Yes. Set changedSince to an ISO date-time to filter reply publication times. Your own workflow must supply the next cutoff and handle any overlap. This does not detect edits, guarantee every new reply, or enable a schedule automatically.

What happens when one URL fails?

Valid rows from other targets are preserved when safe. Read OUTPUT for per-target coverage and empty, unavailable or failed reasons. An inaccessible page alone does not prove the post is private or deleted. Fatal configuration, billing or essential storage failures still fail the run.

Can I run Threads Replies Scraper through an API, schedule, or MCP client?

Yes. Run it with the Apify API, client libraries, schedules, webhooks, integrations, or the Apify MCP server.

How much does it cost to use Threads Replies Scraper?

Runs are charged for the start event and successfully saved replies. Current prices and volume discounts are shown on the Actor's live Pricing tab.

Is it an alternative to the official Threads API?

It is useful for bounded exports of publicly visible reply data. Choose the official API when you need authenticated capabilities or guarantees provided by Meta.

Related Actors

More Threads scrapers

• Threads Profile & Posts Scraper — Collect available public Threads profile details and posts.

• Instagram Comments Scraper — Collect visible public Instagram comment text and available author fields from known post or Reel URLs.
• TikTok Comments Scraper — Collect available public TikTok comments and replies from known video URLs.
• X / Twitter Posts Scraper — Export public X posts for cross-platform research.
• Instagram Profile & Posts Scraper — Collect Instagram post context alongside audience-reply research.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥