Threads Replies Scraper

Export public Threads replies from post or profile URLs for social listening, creator research, sentiment analysis, and conversation monitoring. This Threads scraper includes root-post provenance, author details, engagement, media, and conversation-tree fields, with a Threads API for automated workflows.

Who is it for?

Social listening teams, creator-economy analysts, brand and reputation teams, and researchers can use the Actor to monitor public audience reactions and reconstruct reply conversations.

What you can export

• 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 for conversation-tree analysis
• Monitoring and quality fields such as changedSinceMatched, scrapedAt, and warning

Input example

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

Output example

{
  "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": "DbTnB4JGWEX",
  "depth": 1,
  "authorUsername": "example",
  "authorProfileUrl": "https://www.threads.com/@example",
  "text": "A public reply",
  "mentions": [],
  "hashtags": [],
  "externalUrls": [],
  "likeCount": 3,
  "mediaUrls": [],
  "changedSinceMatched": true,
  "scrapedAt": "2026-08-06T12:00:00.000Z",
  "isPublicSubset": true,
  "warning": "Threads may expose only a public subset; unavailable optional metadata is null."
}

Input settings

Field	Type	Description
postUrls	array	Public Threads post URLs whose replies should be collected.
profileUrls	array	Public profile URLs; the Actor discovers visible posts and collects their replies.
maxRepliesPerThread	integer	Maximum replies saved per thread (1–1000).
maxDepth	integer	Maximum requested conversation depth (1–10).
changedSince	string	Optional ISO date-time cutoff for incremental monitoring.
proxyConfiguration	object	Apify Proxy configuration; SHADER is the default.

Provide at least one post or profile URL.

Output fields

Group	Fields
Source	sourceType, sourceUrl, targetIndex, isPublicSubset, warning
Root post	rootPostId, rootPostCode, rootPostUrl, rootAuthorUsername, rootAuthorUserId, rootAuthorDisplayName, rootText, rootCreatedAt, rootLikeCount, rootReplyCount, rootRepostCount, rootQuoteCount, rootViewCount
Reply edge	replyId, replyCode, replyUrl, parentReplyId, parentAuthorUsername, depth
Author	authorUserId, authorUsername, authorDisplayName, authorProfileUrl, authorProfilePicUrl, authorVerified, authorFediverseEnabled
Content	text, mentions, mentionedAccounts, hashtags, externalUrls, createdAt, createdAtTimestamp
Engagement	likeCount, replyCount, repostCount, quoteCount, shareCount, isLikedByRootAuthor
Media and flags	mediaType, mediaUrls, mediaWidth, mediaHeight, hasAudio, accessibilityCaption, isQuotePost, quotedPostUrl, isRepost, repostedPostUrl, isPaidPartnership, isEdited, replyControl
Monitoring	changedSinceMatched, scrapedAt

Fields unavailable on the public page are returned as null; arrays remain arrays.

Input recipes

Monitor two known posts: add both URLs to postUrls, set maxRepliesPerThread to a bounded value, and schedule the Actor.

Collect recent replies: set changedSince to the last successful monitoring timestamp.

Follow a public profile: put a canonical profile URL in profileUrls; rows retain the originating profile in sourceUrl.

Pricing

The Actor uses pay-per-event pricing: one small start event per run and one reply event for each successfully saved dataset row. See the live Pricing tab for current rates and volume discounts. Failed replies are not charged.

Tips and limits

• Start with one public post and a low reply limit.
• Threads decides which replies are visible to logged-out visitors; the public subset can be smaller than the displayed total.
• Private, removed, restricted, or login-only content is not bypassed.
• Engagement and author metadata can be absent from the public surface.
• Use stable post URLs for recurring monitoring; active threads can change between runs.
• The Actor preserves successful rows when another target fails and reports target failures in the run output.

API usage

cURL

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

JavaScript

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

Use the Apify API client, webhooks, schedules, dataset exports, or integrations to automate downstream analysis.

MCP and AI agents

Connect through the Apify MCP server and enable fetch_cat/threads-replies-scraper.

$claude mcp add apify https://mcp.apify.com

Example MCP client configuration:

{
  "mcpServers": {
    "apify": { "url": "https://mcp.apify.com" }
  }
}

Example prompts:

• “Run fetch_cat/threads-replies-scraper for this Threads post and summarize recurring audience reactions.”
• “Collect up to 50 public replies, then group them by reply depth and author.”

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 and schedule recurring runs. Keep the previous timestamp in your own workflow.

What happens when one URL fails?

Valid rows from other targets are preserved. The run output identifies restricted, removed, empty, or failed targets.

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

• Threads Profile Posts Scraper
• Instagram Comments Scraper
• TikTok Comments Scraper

Support

Open an issue from the Actor's Issues tab with the public target URL, expected behavior, and run ID. Do not include account credentials or private data.