# Threads Search Scraper — Keywords, Hashtags, Accounts (`lergassy/threads-search-scraper`) Actor

Search Meta Threads by keyword or hashtag and get every public post as a row: text, author, time, likes, replies, reposts, images, videos, links and mentions. Top, recent and tag pages in one pass, deduplicated. Finds matching accounts too. No login, no browser.

- **URL**: https://apify.com/lergassy/threads-search-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 Search Scraper** turns a keyword or a hashtag into rows of public Threads posts: text, author, time, likes, replies, reposts, quotes and shares, images and videos, links, mentions and hashtags. It reads the top, recent and tag result pages in one pass and removes duplicates, so a search returns what Threads actually shows a visitor — not one slice of it. It can also return the accounts behind a keyword instead of their posts. No login, no cookies, no browser.

![One run of Threads Search Scraper: posts for a keyword with text, author and engagement.](https://raw.githubusercontent.com/lergassy/apify-actor-assets/main/threads-scraper/threads-scraper-output-table.png)

Paste keywords or #hashtags, click Start, export as JSON, CSV or Excel — or call it from the API and from AI agents.

### What is it for?

Social listening and brand monitoring, tracking a campaign hashtag, watching a competitor's mentions, collecting posts for research, and AI agents asked "what are people saying about X on Threads". Threads' official API only covers your own account; this Actor reads the public pages Threads serves to any visitor, so any public post is in reach.

| Mode | You give | You get |
|---|---|---|
| **Search** | keywords, #hashtags | public posts from the top, recent and tag pages, deduplicated |
| **Accounts** | keywords | people and brands matching the keyword, optionally with full profile details |

`searchTypes` decides which result pages are read (`top`, `recent`, `tags`), `postedAfter` cuts everything older than a date, and `filterKeywords` keeps only posts that contain one of your words.

### 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` | "Muse Spark 1.3 is rolling out today…" · en |
| `createdAt`, `timestamp` | 2026-09-02T19:26:23.000Z · 1788377183 |
| `username`, `userId`, `fullName`, `isVerified`, `profilePicUrl`, `profileUrl` | zuck · 63055343223 · Mark Zuckerberg · true · … |
| `likeCount`, `replyCount`, `repostCount`, `quoteCount`, `shareCount` | 1453 · 196 · 148 · 28 · 78 |
| `mediaType`, `imageUrl`, `videoUrl`, `images[]`, `videos[]` | carousel · … · \[{url,width,height,alt}] · \[{url,thumbnail,hasAudio}] |
| `hashtags`, `mentions`, `urls`, `linkPreview` | \["ai"] · \["natgeo"] · \["https://…"] · {url, title, imageUrl} |
| `isQuote`, `quotedPost`, `isRepost`, `repostedPost` | the quoted or boosted post, inline |
| `source`, `query` | search-top · search-recent · search-tag · the keyword that found the row |

Account rows carry `username`, `userId`, `fullName`, `biography`, `bioLinks`, `websiteUrl`, `emails` and `phones` from the bio, `followerCount`, `isVerified`, `isPrivate`, `profilePicUrl`, `profileUrl`.

### 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 | $0.002 — 1,000 posts for $2 |
| Account match | $0.002 |
| Account with full profile details | $0.004 |

Larger monthly plans get 10–30 % off.

### Notes

Threads shows search results to logged-out visitors, and that is exactly what this Actor reads — public posts only. Private accounts are never opened. How many results a keyword has is Threads' decision, not ours: rare keywords return a handful of posts, and `maxPosts` caps the rest.

Need an account's own posts, its profile and contacts, or a whole conversation? Those live in **Threads Profile Scraper**, **Threads Replies 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.

## `keywords` (type: `array`):

For Search and Accounts. <code>AI agents</code>, <code>#nba</code>, <code>coffee roaster brooklyn</code>. The # is optional.

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

## `searchTypes` (type: `array`):

Search mode: which result pages to combine. Duplicates are removed.

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

## `maxUsersPerKeyword` (type: `integer`):

Accounts mode.

## `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": "search",
  "keywords": [
    "bali"
  ],
  "maxPosts": 50,
  "searchTypes": [
    "top",
    "recent",
    "tags"
  ],
  "includeProfile": false,
  "maxUsersPerKeyword": 20,
  "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": "search",
    "keywords": [
        "bali"
    ],
    "maxPosts": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("lergassy/threads-search-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": "search",
    "keywords": ["bali"],
    "maxPosts": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("lergassy/threads-search-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": "search",
  "keywords": [
    "bali"
  ],
  "maxPosts": 50
}' |
apify call lergassy/threads-search-scraper --silent --output-dataset

```

## MCP server setup

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