# Threads Posts, Search & Replies Scraper (`getdataforu/threads-posts-scraper`) Actor

Threads posts from any public profiles, keyword searches and post links - text, photos, videos, exact likes, replies, reposts, quotes and shares - plus the replies under any post. No login, no proxy needed.

- **URL**: https://apify.com/getdataforu/threads-posts-scraper.md
- **Developed by:** [EMT Crawler](https://apify.com/getdataforu) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.75 / 1,000 results

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Threads Posts, Search & Replies Scraper

Collect **Threads posts** three ways — the **latest posts of any public profiles**, the **top posts for any keyword**, and **any post you link with the replies under it** — with exact **likes, replies, reposts, quotes and shares**, text, photos and videos.

No Threads or Instagram login, no cookies, no API key.

### What it's for

- **Brand and topic monitoring** — run daily on your keywords and competitors' accounts and catch new posts while they are fresh.
- **Campaign reporting** — paste the links of sponsored posts and get exact engagement for each, ready for the client report.
- **Influencer research** — see what a creator posts and how their audience responds.
- **Audience research** — read the replies under a brand's or a creator's post: questions, complaints, praise.
- **Content research** — what is working on Threads for a topic right now.

### What you get for each post

| | |
|---|---|
| **Engagement** | Exact likes, replies, reposts, quotes and shares (not rounded) |
| **Content** | Text, media type (text, photo, video, carousel), photo and video URLs, links, @mentions, hashtags, link preview |
| **Context** | Quoted or reposted post, whether it is a reply and to whom, paid-partnership flag, edited flag, language |
| **Account** | Username, display name, verified badge, user ID |
| **Post** | Post ID, short code, link, date and time; where it came from (`profile`, `search` or `post`) and whether it is a post or a reply |

Real rows from a test run:

| Account | Source | Text | Likes | Replies | Reposts |
|---|---|---|---|---|---|
| nasa | search "nasa" | Spotted: views of a "space jellyfish"… | 39,525 | — | — |
| zuck | profile | Introducing Muse Wonder, our new family of frontier models… | 1,928 | 306 | 137 |
| cristi.baluta | reply to zuck | Can you make that stupid moose to remove… | 16 | 1 | 0 |

### Three ways to collect

| Input | What comes back | Measured |
|---|---|---|
| `usernames` | The account's **latest threads**, as Threads shows them to visitors | 4–10 posts per account |
| `searchQueries` | The **top posts** Threads shows for the keyword, from any account | 22–30 posts per keyword |
| `postUrls` | The post itself plus the **replies** shown under it, each with its own likes | up to ~15 replies per post |

Use any combination in one run. A post found twice (for example in a profile and a search) is saved once and charged once.

### Input

```json
{
  "usernames": ["zuck", "@nasa", "https://www.threads.com/@netflix"],
  "searchQueries": ["pickleball", "world cup"],
  "postUrls": ["https://www.threads.com/@zuck/post/DeZtp-TkQHh"],
  "includeReplies": true
}
```

| Field | Default | Notes |
|---|---|---|
| `usernames` | — | Usernames or profile links. |
| `searchQueries` | — | One keyword per line. |
| `postUrls` | — | threads.com or threads.net post links. |
| `includeReplies` | `true` | Save the replies under linked posts. |
| `includeOwnThreadReplies` | `true` | On profiles, keep the posts where the author continues their own thread. |

At least one username, keyword or post link is required.

### Speed and cost

Measured: **188 posts from 8 profiles, 5 keyword searches and 3 post links in 27 seconds**, every request answered first time. The actor reads Threads directly, without a proxy, which keeps runs fast and very cheap — schedule it as often as you like.

### You only pay for posts you get

Profiles that don't exist, private profiles, searches with no results and deleted posts are never written to the dataset, so they are never charged. They are listed with the reason in `RUN_SUMMARY.failed`.

### Limitations

- **Logged-out visitors see a limited slice of Threads**, and so does this actor: a profile shows its latest few threads (not the full history), a search shows its top ~25 posts, and a post shows its top replies. For a complete history of an account, run the actor on a schedule and keep every run's results.
- View counts are not included — Threads does not show them to visitors.
- Private profiles are not visible without following them.

### Legal

Reads only what Threads shows any visitor without logging in. You are responsible for how you use the data.

# Actor input Schema

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

Usernames or profile links. Each returns the account's latest public threads, as Threads shows them to visitors.

## `searchQueries` (type: `array`):

Each keyword returns the top posts Threads shows for it, from any account.

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

Links to individual posts: exact likes, replies, reposts, quotes and shares - ideal for campaign reporting.

## `includeReplies` (type: `boolean`):

Also save the replies Threads shows under each linked post, with their own likes.

## `includeOwnThreadReplies` (type: `boolean`):

On profiles, keep the posts where the author continues their own thread (marked isReply).

## `maxConcurrency` (type: `integer`):

Each Threads page is about 1 MB of data.

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

Requests go out directly. This proxy is only used when Threads refuses one.

## Actor input object example

```json
{
  "usernames": [
    "zuck",
    "@nasa",
    "https://www.threads.com/@netflix"
  ],
  "searchQueries": [
    "pickleball",
    "world cup"
  ],
  "postUrls": [
    "https://www.threads.com/@zuck/post/DeZtp-TkQHh"
  ],
  "includeReplies": true,
  "includeOwnThreadReplies": true,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `posts` (type: `string`):

Every post and reply: account, text, date, media, exact likes, replies, reposts, quotes, shares, links, mentions and quoted posts.

## `runSummary` (type: `string`):

Posts saved per profile, keyword and link, and inputs that failed with the reason.

# 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 = {
    "usernames": [
        "zuck",
        "nasa"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("getdataforu/threads-posts-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 = { "usernames": [
        "zuck",
        "nasa",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("getdataforu/threads-posts-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 '{
  "usernames": [
    "zuck",
    "nasa"
  ]
}' |
apify call getdataforu/threads-posts-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,getdataforu/threads-posts-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/ZhEuK9wko3cMQO3qM/builds/Z1bxVu9qMYrQJliET/openapi.json