# Threads Replies Scraper — Conversations & Comments (`lergassy/threads-replies-scraper`) Actor

The replies side of Threads as rows: every reply an account wrote with the post it answered, every reply under a post URL, and reposts. Text, author, time, engagement, media, links and reply context on each row. No login, no browser.

- **URL**: https://apify.com/lergassy/threads-replies-scraper.md
- **Developed by:** [Matvey](https://apify.com/lergassy) (community)
- **Categories:** Social media, Agents, MCP servers
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.40 / 1,000 posts

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

**Threads Replies Scraper** covers the conversation side of Meta Threads: every reply an account wrote, each carrying the post it answered; every reply under a post URL you give it; and the posts an account reposted. Each row has text, author, time, likes, replies, reposts and quotes, images and videos, links, mentions and the reply context. No login, no cookies, no browser.

![One run of Threads Replies Scraper: replies with their parent posts, authors and engagement.](https://raw.githubusercontent.com/lergassy/apify-actor-assets/main/threads-scraper/threads-scraper-output-table.png)

Paste usernames or post URLs, click Start, export as JSON, CSV or Excel — or call it from the API and from AI agents.

### What is it for?

Reading what a community actually answers under a post, support and reputation monitoring, sentiment work that needs the comments and not only the original post, conversation datasets for model training, and AI agents asked "what did people reply to this".

| Mode | You give | You get |
|---|---|---|
| **Replies** | usernames | replies the account wrote, each with the post it answered |
| **Thread** | post URLs | the post with its self-thread and all its replies |
| **Reposts** | usernames | posts the account reposted, with the original inline |

### What data does it return?

| Field | Example |
|---|---|
| `id`, `code`, `url` | 3977518562965884838 · Dcy\_A8pGo-m · https://www.threads.net/@zuck/post/Dcy\_A8pGo-m |
| `text`, `language`, `createdAt` | "totally agree, the latency is the hard part" · en · 2026-09-02T19:26:23.000Z |
| `username`, `userId`, `fullName`, `isVerified`, `profileUrl` | who wrote the reply |
| `likeCount`, `replyCount`, `repostCount`, `quoteCount`, `shareCount` | engagement on the reply itself |
| `isReply`, `replyToUsername`, `replyToUserId`, `rootPostUsername` | who is being answered |
| `parentPostId`, `parentPostUrl`, `threadId`, `positionInThread`, `threadLength` | where the reply sits in the conversation |
| `mediaType`, `imageUrl`, `videoUrl`, `images[]`, `videos[]` | media attached to the reply |
| `hashtags`, `mentions`, `urls`, `linkPreview` | \["ai"] · \["natgeo"] · \["https://…"] |
| `isRepost`, `repostedPost`, `repostedBy` | the original post behind a repost |
| `source` | replies · reply-context · thread · reposts |

### How much does it cost?

Pay per row, no start fee, and error rows are free. There is no browser here, so platform usage is close to zero.

| Row | Price |
|---|---|
| Post or reply row | $0.002 — 1,000 replies for $2 |
| Profile (when `includeProfile` is on) | $0.004 |

Larger monthly plans get 10–30 % off.

### Notes

Public conversations only. How deep a thread goes is Threads' decision: `maxRepliesPerPost` caps how many replies are read under one post, and `maxPosts` caps the run.

Need an account's own posts, its profile and contacts, or posts by keyword? Those live in **Threads Profile Scraper**, **Threads Search Scraper** and the all-in-one **Threads Scraper**.

# Actor input Schema

## `mode` (type: `string`):

<b>Posts</b> — an account's own posts, as many as you ask for. <b>Replies</b> / <b>Reposts</b> — what an account answered or boosted. <b>Profile</b> — followers, bio, links and contacts. <b>Search</b> — public posts for keywords and hashtags. <b>Thread</b> — one post with its replies. <b>Accounts</b> — people and brands matching a keyword.

## `usernames` (type: `array`):

For Posts, Replies, Reposts and Profile. Bare name, with @, or the profile URL: <code>zuck</code>, <code>@natgeo</code>, <code>https://www.threads.net/@nasa</code>.

## `postUrls` (type: `array`):

For Thread mode: <code>https://www.threads.net/@zuck/post/Dcy\_A8pGo-m</code>. In Posts mode these are fetched too.

## `startUrls` (type: `array`):

Profile, post, search or tag URLs — each is routed to the matching job automatically.

## `maxPosts` (type: `integer`):

Cap per username or keyword, not per run. Posts mode pages through the whole profile; Search returns what Threads shows a logged-out visitor (usually 20–60 posts per keyword across the top, recent and tag pages).

## `maxRepliesPerPost` (type: `integer`):

Threads shows a logged-out visitor the first ~25 replies of a post.

## `postedAfter` (type: `string`):

<code>YYYY-MM-DD</code>. Older posts are dropped and Posts mode stops paging once it reaches them.

## `filterKeywords` (type: `array`):

Case-insensitive words or phrases; a post is kept when it contains any of them. Empty = keep everything.

## `includeProfile` (type: `boolean`):

Posts, Replies and Reposts modes: also save the account's profile (followers, bio, links, contacts).

## `includeProfileDetails` (type: `boolean`):

Accounts mode: open each account's page for follower count, bio links and contacts (one extra request per account).

## `maxItems` (type: `integer`):

Stop after this many rows in the run.

## `concurrency` (type: `integer`):

How many accounts or keywords are processed at once.

## `proxyConfiguration` (type: `object`):

Apify datacenter proxies work for Threads. If runs end with rate-limit error rows, switch to Residential.

## Actor input object example

```json
{
  "mode": "replies",
  "usernames": [
    "zuck"
  ],
  "maxPosts": 50,
  "maxRepliesPerPost": 100,
  "includeProfile": false,
  "includeProfileDetails": true,
  "maxItems": 10000,
  "concurrency": 4,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `rows` (type: `string`):

One row per post (text, author, time, likes, replies, reposts, quotes, shares, media URLs, links, mentions, hashtags, quoted or reposted post, reply context) or per profile / account (followers, bio, links, emails, phones).

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "replies",
    "usernames": [
        "zuck"
    ],
    "maxPosts": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("lergassy/threads-replies-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "replies",
    "usernames": ["zuck"],
    "maxPosts": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("lergassy/threads-replies-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "replies",
  "usernames": [
    "zuck"
  ],
  "maxPosts": 50
}' |
apify call lergassy/threads-replies-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lergassy/threads-replies-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/qtsTulpEBIjd3wcLg/builds/IXQ6EVu9uevfgeoFc/openapi.json