# Threads Search Scraper - Posts, Users, Replies & Profiles (`seemuapps/threads-search-scraper`) Actor

Search Threads posts by keyword and date, find users, export every reply on a post, and bulk look up profiles with bio, followers and links.

- **URL**: https://apify.com/seemuapps/threads-search-scraper.md
- **Developed by:** [Seemu Scraping](https://apify.com/seemuapps) (community)
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.50 / 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.

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, Users, Replies & Profiles

Search Threads by keyword, find accounts, export the replies on any post and look up profile details in bulk. No login, no cookies, no Threads account needed.

One actor, four modes:

| Mode | You give it | You get |
|------|-------------|---------|
| **Search posts by keyword** | Keywords or #hashtags, optional date range | Matching posts with text, engagement counts, media and author |
| **Search users by keyword** | Keywords or names | Matching accounts, optionally with bio, follower count and bio links |
| **Replies on post URLs** | Threads post URLs | The post plus its replies, and optionally replies to replies |
| **Profile details for usernames** | A list of usernames | Bio, follower count, verified badge, bio links, topics and profile picture |

### What you get

**Posts and replies** (`type: "post"` or `"reply"`)

- Post URL, post ID, shortcode, full text and publish time (`createdAt`)
- Likes, replies, reposts, quotes, and views (views are shown for posts opened by URL)
- Media type (text, image, video, carousel, GIF), image URLs, video URL and alt text
- Topic tag, hashtags, @mentions, links in the text, link preview URL and title
- Quoted post URL, whether the post is a reply and who it replies to
- Author username, display name, user ID, verified badge, profile picture and profile URL
- For replies: `parentPostUrl`, `sourcePostUrl` and `depth` (1 = direct reply, 2 = reply to a reply, ...)
- For search results: the `searchQuery` that found the post

**Profiles** (`type: "profile"`)

- Username, display name, user ID, profile URL, verified badge, private flag
- Biography, follower count, bio links and the topics the profile posts about
- Profile picture (standard and HD)
- For user search results: the `searchQuery` that found the account

Export to JSON, CSV, Excel or Google Sheets from the **Dataset** tab, or pull results through the Apify API.

### Use cases

- **Social listening and brand monitoring**: track what people say on Threads about your brand, product or competitors, day by day
- **Trend and hashtag research**: collect every post on a topic for a date range and see what gets the most engagement
- **Influencer discovery and lead generation**: find creators by keyword, then pull their follower counts, bios and bio links in bulk
- **Audience and sentiment analysis**: export the full reply thread under a viral post for analysis or an LLM
- **Competitor analysis**: compare follower counts and bio links across a list of accounts

### How to use

#### Search posts by keyword

1. Choose **Search posts by keyword**.
2. Add one or more keywords in **Search keywords**. Short keywords and hashtags give the most results.
3. Optional: set **Start date** and **End date** to search a specific period.
4. Set **Max posts per keyword** (default 50) and **Max requests per keyword** (default 10).
5. Run the actor.

Without dates, the actor starts from the latest posts and then goes back one day at a time. With dates, it goes back one day at a time from the end date to the start date. Each day returns up to about 20 posts, so **Max requests per keyword** is roughly how many days get scanned.

**To go further back in time:** the run log ends with a line like `To go further back, set End date to 2026-09-19`. Put that date in **End date** and run again.

#### Search users by keyword

1. Choose **Search users by keyword** and add keywords. Each keyword returns about 10 matching accounts.
2. Turn on **Include full profile details** if you also want bio, follower count and bio links for every account found.

#### Replies on post URLs

1. Choose **Replies on post URLs** and paste one or more post URLs (`threads.com/@user/post/CODE`, `threads.net/...` and `threads.com/t/CODE` all work).
2. Keep **Include the original post** on to get a row for the post itself, with its view count.
3. Turn on **Include replies to replies** to open every reply that has its own replies. **Max requests per post** limits how many reply branches are opened.

Threads shows logged-out visitors only the first 5 to 10 direct replies on a post, and the actor returns the same. With **Include replies to replies** on, the actor also collects the conversations under those replies, several levels deep.

#### Profile details for usernames

1. Choose **Profile details for usernames**.
2. Paste usernames or profile URLs, one per line (with or without `@`).

Private or missing accounts are skipped and noted in the log.

### Input example

```json
{
  "mode": "searchPosts",
  "searchQueries": ["basketball", "#wnba"],
  "startDate": "2026-09-01",
  "endDate": "2026-09-07",
  "maxPostsPerQuery": 100,
  "maxRequestsPerKeyword": 7
}
```

### Output example

Post from a keyword search:

```json
{
  "type": "post",
  "postId": "3993746224234379567",
  "code": "Ddsowf6jDkv",
  "url": "https://www.threads.com/@iamedgardosy/post/Ddsowf6jDkv",
  "text": "Unang biyernes sa Doha, later basketball game naman 🏀",
  "createdAt": "2026-09-25T04:47:52.000Z",
  "likeCount": 32,
  "replyCount": 1,
  "repostCount": 0,
  "quoteCount": 0,
  "viewCount": null,
  "mediaType": "image",
  "imageUrls": ["https://scontent.cdninstagram.com/..."],
  "altText": null,
  "videoUrl": null,
  "topic": null,
  "hashtags": [],
  "mentions": [],
  "links": [],
  "linkPreviewUrl": null,
  "linkPreviewTitle": null,
  "isReply": false,
  "replyToUsername": null,
  "quotedPostUrl": null,
  "authorUsername": "iamedgardosy",
  "authorFullName": "Tito EdSy",
  "authorId": "38941220960",
  "authorIsVerified": false,
  "authorProfilePicUrl": "https://scontent.cdninstagram.com/...",
  "authorProfileUrl": "https://www.threads.com/@iamedgardosy",
  "searchQuery": "basketball",
  "sourcePostUrl": null,
  "parentPostUrl": null,
  "depth": null,
  "isAuthorThread": false
}
```

Profile:

```json
{
  "type": "profile",
  "username": "sportsillustrated",
  "userId": "63496592589",
  "fullName": "Sports Illustrated",
  "profileUrl": "https://www.threads.com/@sportsillustrated",
  "isVerified": true,
  "isPrivate": false,
  "biography": "Sports, sports and more sports.",
  "followerCount": 632515,
  "bioLinks": ["https://lnk.bio/sportsillustrated"],
  "topics": ["UFC Threads", "Boxing Threads", "Wrestling Threads"],
  "profilePicUrl": "https://scontent.cdninstagram.com/...",
  "profilePicUrlHd": "https://scontent.cdninstagram.com/...",
  "searchQuery": null,
  "detailsFetched": true
}
```

### Pricing

You pay per result pushed to the dataset:

- **post-result**: each post or reply row
- **profile-result**: each profile row

Duplicates are removed before charging, so each post is charged once per keyword even when two days overlap.

### Tips

- Want a profile's own recent posts? Use our **Threads Posts Scraper**.
- Keyword search is not case sensitive. Multi-word phrases work, but single words and hashtags return more posts.
- Engagement counts are captured at the time of the run.
- The free plan returns up to 50 results per run. Upgrade to a paid Apify plan to remove the limit.

### FAQ

**Do I need a Threads or Instagram account?**
No. The actor only reads public data.

**Can I get every reply on a post with hundreds of replies?**
No. Threads shows logged-out visitors only the first 5 to 10 direct replies on a post. With **Include replies to replies** on, you also get the conversations under those replies.

**Why do some posts in a date search fall a few hours outside the day?**
Threads groups posts by day in its own time zone, so posts close to midnight UTC can show up in the day before or after.

# Actor input Schema

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

Search posts: keyword search with optional date range. Search users: find accounts matching a keyword. Replies on post URLs: the post plus its replies. Profile details: bio, follower count, verified badge and bio links for a list of usernames.

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

Keywords, phrases or #hashtags to search for, one per line. Used by 'Search posts' and 'Search users'. Short keywords return the most results.

## `startDate` (type: `string`):

Search posts only: oldest day to include (YYYY-MM-DD). Leave empty to start from the latest posts and walk back day by day until the limits below are reached.

## `endDate` (type: `string`):

Search posts only: newest day to include (YYYY-MM-DD). Leave empty for today. Set it to continue an earlier run further back in time.

## `maxPostsPerQuery` (type: `integer`):

Search posts only: stop after this many unique posts for each keyword. 0 = no limit (bounded by Max requests per keyword).

## `maxRequestsPerKeyword` (type: `integer`):

Search posts only: each request covers one day and returns up to about 20 posts. This caps how many days are scanned per keyword.

## `includeProfileDetails` (type: `boolean`):

Search users only: also fetch bio, follower count and bio links for every user found. Without it you get username, name, verified badge and picture.

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

Replies mode only: Threads post URLs, one per line (threads.com/@user/post/CODE, threads.net links and threads.com/t/CODE all work).

## `includeOriginalPost` (type: `boolean`):

Replies mode only: add a row for the post itself (and any follow-up posts the author added to the thread) before its replies.

## `includeNestedReplies` (type: `boolean`):

Replies mode only: also open every reply that has its own replies and collect those (one extra request per reply branch, bounded by Max requests per post).

## `maxRepliesPerPost` (type: `integer`):

Replies mode only: stop after this many reply rows for each post. 0 = no limit.

## `maxRequestsPerPost` (type: `integer`):

Replies mode only: cap on requests used for one post, including the first one. Only matters when replies to replies are included.

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

Profile details mode only: Threads usernames or profile URLs, one per line (with or without @).

## Actor input object example

```json
{
  "mode": "searchPosts",
  "searchQueries": [
    "basketball"
  ],
  "maxPostsPerQuery": 15,
  "maxRequestsPerKeyword": 10,
  "includeProfileDetails": false,
  "postUrls": [],
  "includeOriginalPost": true,
  "includeNestedReplies": false,
  "maxRepliesPerPost": 100,
  "maxRequestsPerPost": 10,
  "usernames": []
}
```

# Actor output Schema

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

Rows with type 'post' or 'reply': postId, code, url, text, createdAt, likeCount, replyCount, repostCount, quoteCount, viewCount, mediaType, imageUrls, videoUrl, topic, hashtags, mentions, links, linkPreviewUrl, author fields, searchQuery, parentPostUrl, depth. Rows with type 'profile': username, fullName, profileUrl, isVerified, biography, followerCount, bioLinks, topics, profilePicUrl.

# 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": "searchPosts",
    "searchQueries": [
        "basketball"
    ],
    "maxPostsPerQuery": 15,
    "postUrls": [],
    "usernames": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("seemuapps/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": "searchPosts",
    "searchQueries": ["basketball"],
    "maxPostsPerQuery": 15,
    "postUrls": [],
    "usernames": [],
}

# Run the Actor and wait for it to finish
run = client.actor("seemuapps/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": "searchPosts",
  "searchQueries": [
    "basketball"
  ],
  "maxPostsPerQuery": 15,
  "postUrls": [],
  "usernames": []
}' |
apify call seemuapps/threads-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seemuapps/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/LfKaeCS5xLg7w9gPv/builds/5C3AnwNQ5YV3G5MJ6/openapi.json