Threads Search Scraper

Threads Search Scraper is an Apify Actor for people and teams that need Meta Threads search results in structured form. It accepts keyword searches for public Threads posts or username searches for public Threads user profiles, and it returns one record per matched result. The output includes fields such as post text, author identifiers, engagement counts, timestamps, profile URLs, verification flags, and the originating query so you can route each record into downstream analysis, monitoring, or agent workflows. It is cookieless, provider-backed, and usable through Apify MCP.

Best fit and connected workflows

Use this Actor when you want search-result lists from Threads rather than a single post URL or a full profile history. It fits well with:

• topic monitoring from keyword searches across public Threads posts
• account discovery from username-fragment searches
• data prep for dashboards, CRM enrichment, content research, and AI agent steps
• tool-style integrations through Apify MCP, where a single search query produces structured dataset records

If your workflow starts with a topic, hashtag, or handle fragment, this Actor gives you a clean search layer before any follow-up enrichment or analysis.

Focused standalone workflow

This Actor is designed as a focused standalone workflow.

Practical scenario

Maya, a social media analyst, starts with the keyword ai agents and sets searchType to posts. The run returns records with text, authorUsername, likeCount, replyCount, repostCount, quoteCount, takenAt, url, and query. Maya uses those fields to identify posts that deserve manual review, then shares the post URLs with a content lead for follow-up tracking.

Input

Field	Type	Default	Description
searchType	string enum	posts	Search mode. posts searches public Threads post text by keyword. users searches public Threads accounts by username fragment.
queries	array of strings	["ai agents"]	One or more independent search terms. Results are merged and de-duplicated across queries.
maxResults	integer	100	Total cap across all queries for cost control.
maxResultsPerQuery	integer	25	Cap per query before the Actor moves on to the next query.
startDate	string	-	Earliest post date in YYYY-MM-DD format. Applied only in posts mode.
endDate	string	-	Latest post date in YYYY-MM-DD format. Applied only in posts mode.
provider	string enum	auto	Data provider selection: auto, scrapecreators, or sociavault.

Focused input example

{
  "searchType": "posts",
  "queries": ["ai agents", "vibe coding"],
  "maxResults": 20,
  "maxResultsPerQuery": 10,
  "startDate": "2026-01-01",
  "endDate": "2026-06-30",
  "provider": "auto"
}

Output

The Actor writes results to the default dataset. The dataset record shape depends on the selected search mode.

Mode	Record fields
posts	text, authorUsername, authorFullName, likeCount, replyCount, repostCount, quoteCount, takenAt, url, query
users	username, fullName, isVerified, isActiveOnThreads, profileUrl, query

Illustrative output record

{
  "text": "I literally have a business that is 100% automated by my AI agents",
  "authorUsername": "kevbuildsai",
  "authorFullName": "Kev | AI Agent Automation",
  "likeCount": 30,
  "replyCount": 11,
  "repostCount": 0,
  "quoteCount": 0,
  "takenAt": "2026-06-15T10:23:34.000Z",
  "url": "https://www.threads.com/@kevbuildsai/post/DZlvKb5FPll",
  "query": "ai agents"
}

How it works

This Actor searches Meta Threads through provider-backed search APIs. The manifest shows two backend providers: ScrapeCreators and SociaVault. In auto mode, the Actor tries ScrapeCreators first and falls back to SociaVault when the primary provider returns an empty result or fails. The live contract also shows that both providers return the same fields.

The input schema supports two search modes:

• posts for public post text searches by keyword
• users for public account searches by username fragment

For posts, optional date filtering is available through startDate and endDate. The dataset views in the contract define how results are presented in the Apify Console for each mode.

Pricing

This Actor uses Pay per event plus Apify platform usage. The live contract defines these charge events:

• Actor start
• Post scraped
• User found

Each returned post or user is billed as a separate event, and the Actor also charges once per run for initialization. For example, a run that returns one hundred results in one mode is billed for one Actor start event and one hundred result events. For the latest pricing details, including the live tab values and any platform usage charges, open the Pricing tab on the Actor page.

Use with AI agents (MCP)

This Actor is available as an Apify Actor usable through Apify MCP. The exact Actor identity is khadinakbar/threads-search-scraper.

Tool purpose: run a Threads search and receive structured dataset rows that an agent can inspect, summarize, classify, or hand off to another step.

Search Threads for public posts about "ai agents", return the top 10 results, and include the post URL, author, counts, timestamp, and the originating query for each record.

Output interpretation:

• In posts mode, each row represents one matched public post.
• In users mode, each row represents one matched public account.
• The query field shows which search term produced the record.
• The dataset is the source of truth for run results.
• The output schema exposes a results link to the dataset items endpoint.
• If you use multiple queries, the Actor merges and de-duplicates results across those queries.
• maxResults controls the total run cap, and maxResultsPerQuery controls per-query yield.

Scope and provenance:

• Results come from public Threads search.
• The Actor is cookieless.
• Provider selection can be set to auto, scrapecreators, or sociavault.

Pagination and cost guidance:

• Each query typically returns about 20 to 25 results from the provider search endpoint.
• Larger maxResultsPerQuery values rarely add more beyond that range.
• Use maxResults to cap the total number of billed records across all queries.

Apify API example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const input = {
  searchType: 'posts',
  queries: ['ai agents'],
  maxResults: 10,
  provider: 'auto',
};

const run = await client.actor('khadinakbar/threads-search-scraper').call(input);

const datasetId = run.defaultDatasetId;
const { items } = await client.dataset(datasetId).listItems();

console.log('Dataset items:');
for (const item of items) {
  console.log(item);
}

Best results and outcome guidance

Pick posts when you want topic or hashtag monitoring, and pick users when you want account discovery from a handle fragment. Keep queries specific enough to match the search intent you want to analyze. If you are collecting posts, use startDate and endDate when a time window matters. For broader coverage, execution multiple queries and review the merged dataset output.

Design note

I found that the live contract exposes separate dataset views for posts and users, and each view transforms to a different field set. That makes the mode-specific output shape clear and keeps the README aligned with the actual record contract.

FAQ

Is this Actor for a single Threads post URL?

This Actor is built for search-result lists. Use a post-detail workflow for a single post URL, or a profile workflow for a full account page.

Can I search public Threads users by name fragment?

Yes. Set searchType to users and pass username fragments in queries, such as openai.

Can I search public Threads posts by topic?

Yes. Set searchType to posts and pass keywords or hashtags in queries, such as ai agents or climate tech.

What happens when I use multiple queries?

Each query runs independently, then the Actor merges and de-duplicates the results before writing them to the dataset.

Which provider should I choose?

auto is the default. It uses ScrapeCreators first and then SociaVault if needed. You can also force either provider directly.

Responsible use

Use the results in line with Meta's public access terms and applicable law. This Actor is intended for public Threads search data, structured analysis, and approved automation workflows.