# Threads Search Scraper - Posts by Keyword & Hashtag, No Login (`alom/threads-search-scraper`) Actor
Search Threads posts by keyword or #hashtag without logging in: text, author, likes, replies, reposts, views, media, links and date. Top or newest first, 60-85 posts per keyword, filters for likes, replies, language and date. From $1.50 per 1,000 posts.
- **URL**: https://apify.com/alom/threads-search-scraper.md
- **Developed by:** [Alom Dev](https://apify.com/alom) (community)
- **Categories:** Social media, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet
## Pricing
from $1.50 / 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 Search Scraper: Posts by Keyword & Hashtag, No Login
**Search Threads posts by keyword or #hashtag** and get them as a table: one row per post with the text, author,
likes, replies, reposts, view count, media, links, language and date. Top posts or newest first, with filters so you
keep only the posts worth reading.
- **No login needed.** It reads what a logged-out visitor of threads.com sees. No account of yours is involved.
- **60-85 posts per keyword, not 20.** Threads shows logged-out visitors one page of about 20 results. This Actor
opens several result pages (keyword search, tag search, the tag page) from fresh IPs and merges them.
- **Filters:** minimum likes, minimum replies, language and date window. Posts that don't pass are not charged.
- **View counts** ("423K views") on request, and a guessed `language` on every post.
- **Only new posts on a schedule.** Monitoring mode skips posts an earlier run returned, and you don't pay for them.
- Export to CSV, Excel or JSON, or pull results through the Apify API, Make, Zapier or n8n.
This Actor is a focused version of the [Threads Scraper](https://apify.com/alom/threads-scraper) (same code, same
prices). Use the Threads Scraper if you also need profiles, a profile's posts or the replies under a post.
### What can you use it for?
- **Brand and product mentions:** what people write about your brand, product or competitor.
- **Hashtag research:** the top posts and the newest posts for a #hashtag, with engagement counts.
- **Trend and content research:** which posts on a topic get the likes and views.
- **Social listening for AI agents:** a clean, filtered feed for Claude, ChatGPT or Cursor through MCP (below).
### Input
| Field | What it does |
|---|---|
| `searchQueries` | Keywords, `#hashtags`, or threads.com search / `/tag/` URLs. |
| `searchSort` | `top` (Threads' order, default) or `recent` (newest first). |
| `maxPosts` | Max posts per keyword. Default 50. |
| `requireKeywordMatch` | Keep only posts whose text, topic tag or link title contains the keyword. Default off. |
| `postedAfter` / `postedBefore` | Date window, e.g. `2026-10-01` or `7 days`. |
| `minLikes` / `minReplies` | Keep only posts with at least this many likes / replies. |
| `languages` | Keep only posts in these languages, e.g. `["en"]`. Posts too short to tell are kept. |
| `includeViews` | Fill `viewCount` on every post. One extra request per post, about 1.5 s each, not charged. Default off. |
| `onlyNewSinceLastRun` + `monitorName` | Skip posts an earlier run with the same monitor name returned. |
| `sessionCookie` | Optional, never required: your own logged-in cookie unlocks Threads' real Recent tab with deep paging. At your own risk. |
```json
{ "searchQueries": ["espresso machine", "#coffee"], "maxPosts": 50 }
```
```json
{ "searchQueries": ["ai agents"], "searchSort": "recent", "minLikes": 10, "languages": ["en"], "includeViews": true }
```
```json
{ "searchQueries": ["yourbrand", "#yourbrand"], "searchSort": "recent", "onlyNewSinceLastRun": true, "monitorName": "brand" }
```
#### Switching from another Threads search scraper?
Keep your input. These field names are accepted as they are: `searchQuery` (one keyword) or `keywords` (a list),
`sort` (`top` / `recent`), `sortByRecent` (true / false), `after` / `before` (dates) and `maxItemsPerKeyword`.
### Output example
```json
{
"type": "post",
"postId": "3741234567890123456",
"code": "DdXmpl3ExAm",
"url": "https://www.threads.com/@example_cafe/post/DdXmpl3ExAm",
"text": "Finally dialed in the new espresso machine. 18g in, 36g out, 28 seconds ☕",
"username": "example_cafe",
"fullName": "Example Cafe",
"isVerified": false,
"likeCount": 312,
"replyCount": 41,
"repostCount": 6,
"quoteCount": 2,
"viewCount": 18430,
"mediaType": "image",
"media": [{ "type": "image", "url": "https://scontent…jpg", "width": 1440, "height": 1800 }],
"hashtags": [],
"topicTag": "Coffee Threads",
"language": "en",
"keywordMatch": true,
"searchKeyword": "espresso machine",
"date": "2026-10-14T08:12:40.000Z",
"source": "search:espresso machine",
"scrapedAt": "2026-10-16T09:00:00.000Z"
}
```
(The post above is made up; the fields are what you get.) Every post also has `urls`, `mentions`, `linkPreview`,
`quotedPost`, `isReply`, `isPaidPartnership`, `isAiGenerated` and more; see the
[Threads Scraper](https://apify.com/alom/threads-scraper) for the full list. `viewCount` is `null` unless
`includeViews` is on. Values Threads doesn't show are `null`, never a made-up `0`.
### How much does it cost?
The same prices as the Threads Scraper: **from $1.50 per 1,000 posts**, plus $0.005 per run. Platform usage
(compute, proxy) is included.
| Apify plan | Price per 1,000 posts |
|---|---|
| Free | $2.50 |
| Starter (Bronze) | $2.00 |
| Scale (Silver) | $1.75 |
| Business (Gold) and above | $1.50 |
Two keywords x 50 posts cost **$0.25** on the Free plan. You pay only for rows you receive: posts removed by your
filters and posts a monitor already returned are free.
### Monitoring (only new posts)
Turn on **"Only new posts since my last run"**, give it a name (e.g. `brand`), set the order to **Recent** and
schedule the run in Apify Console. Each run returns only posts you haven't received yet. For a monitor with these
settings already on, see the [Threads Hashtag & Keyword Monitor](https://apify.com/alom/threads-keyword-monitor).
### Use it from AI agents (Claude, ChatGPT, Cursor and other MCP clients)
Add `https://mcp.apify.com/?tools=alom/threads-search-scraper` as a connector (Claude: Settings → Connectors → Add
custom connector; Claude Code: `claude mcp add --transport http threads-search "https://mcp.apify.com/?tools=alom/threads-search-scraper"`)
and sign in with your Apify account. Then ask, for example: *"Find English posts about espresso machines from this
week with at least 10 likes and summarise the complaints."* Keep `maxPosts` at 10-30 so the answer fits the context.
### Limitations
- **About 60-85 posts per keyword** without login. That is what several logged-out result pages add up to, not every
post ever written. With your own session cookie the Recent tab pages much deeper (300 recent posts for "news" in our
test, versus 155 without).
- **"Recent" without a cookie** sorts the posts found newest first; it is not Threads' own Recent tab.
- **Threads' search is loose:** it also returns related posts that don't contain the keyword. Every row has
`keywordMatch`; turn on `requireKeywordMatch` to drop them.
- **View counts** add about 1.5 s per post and are missing on some small, new posts (33 of 40 search posts had one in
our test).
### FAQ
**Do I need a Threads or Instagram account?** No. Nothing is logged in by default, so there is nothing to ban.
**Can I search for posts from one account?** Use the [Threads Scraper](https://apify.com/alom/threads-scraper) with
the username: it pages through the account's posts, which is more complete than search.
**Is it legal?** The Actor collects only what Threads shows publicly without login. Posts are personal data: check
that your use has a lawful basis (GDPR and similar laws) before you store or process them.
### More scrapers from the same developer
- [Threads Scraper](https://apify.com/alom/threads-scraper): posts, profiles, replies, reposts, keyword and hashtag search, account search
- [Threads Profile Scraper](https://apify.com/alom/threads-profile-scraper): followers, bio, bio links and contacts of any Threads account
- [Threads Replies Scraper](https://apify.com/alom/threads-replies-scraper): the replies under any Threads post with whole reply threads
- [Threads Hashtag & Keyword Monitor](https://apify.com/alom/threads-keyword-monitor): only the new posts for your keywords and #hashtags, for scheduled runs
- [Threads Account Finder](https://apify.com/alom/threads-lead-finder): Threads accounts by keyword with followers, bio links and the contacts they list
- [Google Trends API & Scraper](https://apify.com/alom/google-trends-scraper): interest over time, regions, related queries and Trending Now
- [YouTube Scraper](https://apify.com/alom/youtube-scraper): videos, channels, Shorts, comments, subtitles and community posts without the API quota
### Feedback
Missing a field, found a bug, or need a feature? Open an issue in the **Issues** tab and I'll take a look. If this
Actor saved you time, a short review on the Store page helps other people find it.
# Actor input Schema
## `searchQueries` (type: `array`):
Keywords, #hashtags, or threads.com search / /tag/ URLs. Threads shows logged-out visitors ~20 posts per result page, so the Actor opens several result pages (keyword search, tag search, tag page) from fresh IPs and merges them: typically 60-85 unique posts per keyword. In accounts mode: keywords to find profiles by (up to 100 per keyword). In the profile modes: keywords only flag matching rows (keywordMatch).
## `searchSort` (type: `string`):
Recent returns the posts found newest first. The real "Recent" tab of Threads needs a logged-in account: with your own session cookie (below) it is used, without one the Actor sorts what it found.
## `requireKeywordMatch` (type: `boolean`):
Threads' search also returns loosely related posts. Turn on to drop hits whose text, topic tag or link title does not contain the keyword (dropped posts are not charged). Every search row has keywordMatch either way.
## `maxPosts` (type: `integer`):
Threads shows logged-out visitors ~20 posts per result page; the Actor merges several result pages, typically 60-85 unique posts per keyword. With your own session cookie the Recent tab pages much deeper.
## `postedAfter` (type: `string`):
Date (UTC), ISO timestamp or relative like 7 days.
## `postedBefore` (type: `string`):
Date (UTC) or ISO timestamp (exclusive).
## `minLikes` (type: `integer`):
Keep only posts with at least this many likes. Leave empty for no limit. Handy for search, where many results have no engagement at all.
## `minReplies` (type: `integer`):
Keep only posts with at least this many replies. Leave empty for no limit.
## `languages` (type: `array`):
Keep only posts in these languages, as two-letter codes: en, es, pt, fr, de, ja, ko, zh, ru… The language is guessed from the text of each post (see the language field). Posts too short to tell are kept.
## `includeViews` (type: `boolean`):
Fill viewCount (the number Threads shows under a post, e.g. 423K views) on every post. Each count is read from the post's own page: one extra request per post, so the run takes longer. Not charged extra. A post you give by URL always has its view count.
## `onlyNewSinceLastRun` (type: `boolean`):
Skip posts an earlier run with the same monitor name already returned (not charged). Pair with a Schedule to get only fresh posts. For a dedicated monitor see Threads Hashtag & Keyword Monitor.
## `monitorName` (type: `string`):
Keep separate memories for different monitors (e.g. competitors-daily). Defaults to default.
## `sessionCookie` (type: `string`):
Optional and never required. Paste the cookies of a threads.com tab where you are logged in (the Cookie header, or a JSON export; at least sessionid, ideally also csrftoken and ds_user_id). Searches then use Threads' real "Recent" tab and page through it like the app (about twice as many recent posts in our tests). Requests are then made as your account (one IP, at most 2 in parallel): Meta may rate-limit, checkpoint or ban accounts that scrape, so use a spare account. If the cookie is invalid or expired, the run says so and continues without it. Stored encrypted, never logged or returned.
## `maxConcurrency` (type: `integer`):
Profiles / posts / keywords processed in parallel.
## `proxyConfiguration` (type: `object`):
The default Apify datacenter proxy works and is included in the price. If Threads starts blocking it, the run switches to residential proxies by itself (logged).
## Actor input object example
```json
{
"searchQueries": [
"espresso machine",
"#coffee"
],
"searchSort": "top",
"requireKeywordMatch": false,
"maxPosts": 50,
"includeViews": false,
"onlyNewSinceLastRun": false,
"maxConcurrency": 3,
"proxyConfiguration": {
"useApifyProxy": true
}
}
```
# Actor output Schema
## `results` (type: `string`):
No description
# 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 '' with your token
const client = new ApifyClient({
token: '',
});
// Prepare Actor input
const input = {
"searchQueries": [
"espresso machine",
"#coffee"
]
};
// Run the Actor and wait for it to finish
const run = await client.actor("alom/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 '' with your token.
client = ApifyClient("")
# Prepare the Actor input
run_input = { "searchQueries": [
"espresso machine",
"#coffee",
] }
# Run the Actor and wait for it to finish
run = client.actor("alom/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 '{
"searchQueries": [
"espresso machine",
"#coffee"
]
}' |
apify call alom/threads-search-scraper --silent --output-dataset
```
## MCP server setup
```json
{
"mcpServers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,alom/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 ` 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/55npK0784A68v0Qbq/builds/IndBEdVw3RaSfjctI/openapi.json