# 🧵 Threads Scraper — Profiles, Posts, Replies & Keyword Search (`nominated_tupelo/threads-scraper`) Actor

🧵 Scrape public Threads profiles, posts, replies, and keyword search — no login, no API key. Get captions, engagement counts, hashtags, mentions, and follower data. Ideal for marketers, researchers, and AI data pipelines.

- **URL**: https://apify.com/nominated\_tupelo/threads-scraper.md
- **Developed by:** [kade](https://apify.com/nominated_tupelo) (community)
- **Categories:** Social media, Lead generation, AI
- **Stats:** 3 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 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.

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 Scraper — Profiles, Posts, Replies & Keyword Search

**Threads Scraper** extracts public data from [Threads (by Meta)](https://www.threads.net/) — **no login, no API key, no Meta developer account**. Give it usernames, a search query, or a post URL and it returns profiles, posts, replies, captions, engagement counts (likes, replies, reposts), hashtags, mentions, follower counts, timestamps, and media URLs as structured JSON.

Unlike profile-only Threads actors, this one covers **posts, replies, AND keyword search** in a single Actor.

### Why use Threads Scraper?

- **Find and monitor influencers** — pull follower counts and engagement to rank accounts.
- **Track brand and topic mentions** — keyword-search Threads for any term.
- **Build datasets for analytics or AI** — continuously collect captions, hashtags, and engagement for training or trend analysis.
- **Competitive research** — watch competitors' posting cadence and reception.
- **Lead generation** — collect public profile data and bio links at scale.

### How it works

Uses a headless Firefox browser (Playwright) to load threads.net and acquire session tokens, then queries the internal GraphQL API directly for efficient bulk collection. Residential proxies are recommended for reliability against Meta's bot detection. Rate limits are respected with automatic backoff.

### Input

| Field | Type | Description |
|-------|------|-------------|
| `mode` | string | `profiles` / `posts` / `search` / `replies` |
| `usernames` | array | Target usernames (without @) |
| `searchQuery` | string | Keyword for search mode |
| `postUrl` | string | Full post URL for replies mode |
| `maxPosts` | integer | Max posts per user (default 50) |
| `maxReplies` | integer | Max replies (default 50) |
| `maxSearchResults` | integer | Max search results (default 50) |
| `includeProfile` | boolean | Include profile metadata in posts output |
| `proxyConfig` | object | Apify proxy config (residential recommended) |

#### Example input

```json
{
  "mode": "posts",
  "usernames": ["zuck", "mark"],
  "maxPosts": 25,
  "includeProfile": true,
  "proxyConfig": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}
```

### Output

Each dataset item is a `post`, `profile`, or `search_result` record.

**Post record:**

```json
{
  "type": "post",
  "postId": "3456789012345678901",
  "username": "zuck",
  "text": "Sharing an update on...",
  "likeCount": 12345,
  "replyCount": 567,
  "repostCount": 89,
  "hashtags": ["meta", "ai"],
  "mentions": ["mark"],
  "timestamp": 1718000000,
  "mediaUrls": ["https://.../"],
  "url": "https://www.threads.net/@zuck/post/..."
}
```

**Profile record:**

```json
{
  "type": "profile",
  "username": "zuck",
  "fullName": "Mark Zuckerberg",
  "bio": "...",
  "followerCount": 12000000,
  "followingCount": 800,
  "isVerified": true,
  "profilePicUrl": "https://.../",
  "url": "https://www.threads.net/@zuck"
}
```

### Pricing

Pay per result at **$0.50 per 1,000 items**. Example: scraping 25 posts each from 100 profiles = 2,500 items ≈ **$1.25** plus Apify platform compute/proxy usage. No subscription, no minimums — you pay only for what you scrape.

### FAQ

**Is this legal?** This Actor accesses only publicly available Threads data. No authentication is bypassed and no login is required. Always comply with applicable data protection laws (GDPR, CCPA) when processing personal data.

**Do I need a Meta account or API key?** No. The Actor needs neither.

**Why residential proxies?** Meta applies bot detection; residential proxies materially improve reliability and success rate.

# Actor input Schema

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

What to scrape: 'profiles' (profile info), 'posts' (user posts), 'search' (keyword search), 'replies' (replies to a post).

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

Threads usernames to scrape (without @). Used in profiles and posts modes.

## `searchQuery` (type: `string`):

Keyword to search (used in search mode).

## `postUrl` (type: `string`):

Full URL of a Threads post to get replies for (used in replies mode). e.g. https://www.threads.net/@zuck/post/abc123

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

Maximum number of posts to scrape per user.

## `maxReplies` (type: `integer`):

Maximum number of replies to scrape in replies mode.

## `maxSearchResults` (type: `integer`):

Maximum number of search results to return.

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

When scraping posts, also include the profile metadata for each user.

## `proxyConfig` (type: `object`):

Apify proxy settings. Residential proxies recommended for Threads.

## Actor input object example

```json
{
  "mode": "posts",
  "usernames": [],
  "maxPosts": 50,
  "maxReplies": 50,
  "maxSearchResults": 50,
  "includeProfile": true,
  "proxyConfig": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("nominated_tupelo/threads-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("nominated_tupelo/threads-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 '{}' |
apify call nominated_tupelo/threads-scraper --silent --output-dataset

```

## MCP server setup

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