# Threads Search Scraper - Posts by Keyword or Tag (`aolmo/threads-search`) Actor

Search Threads by keyword or tag without login: the posts Threads shows to visitors (15-25 per query, top or most recent) with author, text, date, likes, replies, reposts, quotes, media and links. New posts flagged on scheduled runs for social listening. $0.0005 per post.

- **URL**: https://apify.com/aolmo/threads-search.md
- **Developed by:** [Antonio del Olmo Tena](https://apify.com/aolmo) (community)
- **Categories:** Social media
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 post founds

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?

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

Search Threads by keyword or tag without logging in, without API keys and without cookies. Type keywords or #tags and get one row per post Threads shows to visitors (15-25 per query, the top posts or the most recent ones) with author, text, date, likes, replies, reposts, quotes, media and links. Schedule it and new posts are flagged: social listening, brand and competitor mentions, trend research and content discovery at $0.0005 per post.

The Actor reads exactly what Threads renders for a logged-out visitor on the search page. No login, no API quota.

### What you get

**Post** (one row each): `code`, `url`, `username`, `text`, `takenAt`, `type` (text, image, video or carousel), `likes`, `replies`, `reposts`, `quotes`, `reshares`, `isReply`, `replyTo`, `image`, `videoUrl`, `mediaCount`, `linkUrl`, `quotedPostCode`, `repostedPostCode`, `topic`, `position`.

**Search**: `query`, `searchType` (`default` keyword or `tags`), `recent`, `searchUrl`, `postsFound`.

**Changes** on scheduled runs: `isNew` is true for posts that were not in the results of the previous run (null on the first run).

Searches without results return a single row with `postsFound: 0` and are not charged.

### How to use it

1. Open the **Input** tab.
2. Add **Keywords or tags**, one per line (up to 500 per run): `web scraping`, `your brand name` or `#ai` (a leading `#` searches the tag).
3. Optionally turn on **Most recent first** to get the newest posts instead of the top ones.
4. Click **Start** and export the rows as JSON, CSV or Excel.
5. Schedule the Actor (hourly, daily) to get a row with `isNew: true` for every new post that mentions your keywords.

### Input

```json
{
  "queries": ["web scraping", "#ai"],
  "recent": true
}
```

### Output

One row per post:

```json
{
  "query": "web scraping",
  "searchType": "default",
  "recent": true,
  "postsFound": 17,
  "position": 1,
  "code": "DNj2xkHyoWF",
  "url": "https://www.threads.com/@saboo_shubham_/post/DNj2xkHyoWF",
  "username": "saboo_shubham_",
  "text": "Firecrawl v2 API just made web scraping 10x easier...",
  "takenAt": "2026-10-15T14:20:00.000Z",
  "likes": 91,
  "replies": 4,
  "reposts": 12,
  "isNew": null,
  "timestamp": "2026-10-19T10:00:00.000Z"
}
```

### Pricing

Pay per event: **$0.0005 per post** and **$0.001 per new post** detected on a scheduled run. Searches without results are free. A run of 100 keywords with 20 posts each costs $1.

### Limits and notes

- Threads shows visitors one page of results per query (15-25 posts) without pagination. Use several keywords or the **Most recent first** option to cover more.
- The Actor never bypasses logins, CAPTCHAs or rate limits.

### Related Actors

- **Threads Profile Scraper**: followers, bio and the latest posts of a profile.
- **Threads Post Scraper**: a post with its replies.
- **LinkedIn Post Search Scraper**, **Reddit Scraper**: keyword search on other networks.

# Actor input Schema

## `queries` (type: `array`):

One per line: a keyword or phrase (web scraping) or a tag (#ai). Up to 500 per run.

## `recent` (type: `boolean`):

Most recent posts instead of the top posts.

## `searchType` (type: `string`):

default: posts matching the keyword; tags: posts with the tag.

## `product` (type: `string`):

Internal. Leave as is.

## Actor input object example

```json
{
  "queries": [
    "web scraping",
    "#ai"
  ],
  "recent": false,
  "searchType": "default",
  "product": "threads-search"
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset items: url, changed, events, data, timestamp and error (when the target failed).

# 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 = {
    "queries": [
        "web scraping",
        "#ai"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("aolmo/threads-search").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 = { "queries": [
        "web scraping",
        "#ai",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("aolmo/threads-search").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 '{
  "queries": [
    "web scraping",
    "#ai"
  ]
}' |
apify call aolmo/threads-search --silent --output-dataset

```

## MCP server setup

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

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/FTtPBPaCzy403Qlxf/builds/AeFgfZ9QIfZT6g1oJ/openapi.json