Search public Threads posts by keyword and export clean, query-attributed data for brand monitoring, PR, creator research, trend discovery, and campaign analysis. This Threads scraper collects public post URLs, text, authors, timestamps, media, and visible engagement without asking for a Threads or Instagram login.
Buyer workflows
- Monitor recent brand or product mentions on Threads.
- Compare campaign phrases in one bounded run.
- Export public Threads posts to JSON, CSV, Excel, or an API integration.
- Track industry conversations with an optional publication-date boundary.
- Distinguish a genuine no-match result from an upstream challenge or login wall.
Input
The Actor starts with a useful artificial intelligence query. Replace it with one or more terms and choose the total post limit and sort order. Less common controls are grouped under Advanced options.
{
"searchQueries": ["climate tech", "renewable energy"],
"sort": "recent",
"maxItems": 30,
"sinceDate": "2026-09-01",
"includeReplies": false,
"failOnBlocked": true
}
| Field | Purpose |
|---|---|
searchQueries |
Keywords or phrases to search in public Threads results. |
maxItems |
Maximum unique posts saved across all queries. |
sort |
top, or recent to order visible results newest-first. |
sinceDate |
Optional ISO date/time lower bound. |
includeReplies |
Include posts visibly identified as replies. |
failOnBlocked |
Fail instead of returning a misleading empty dataset when access is blocked. |
proxyConfiguration |
Optional connection settings under Advanced options. |
Output
Each dataset row contains the input query, stable id, canonical url, visible text, timestamp, nested author, public media, visible engagement counts, and reply context.
{
"query": "climate tech",
"id": "example-post-id",
"url": "https://www.threads.com/@example/post/example-post-id",
"text": "A public post about climate tech",
"timestamp": "2026-09-20T12:00:00.000Z",
"author": {
"username": "example",
"displayName": "Example Creator",
"profileUrl": "https://www.threads.com/@example"
},
"media": [],
"likes": 12,
"replies": 2,
"reposts": 1,
"quotes": 0,
"views": null,
"isReply": false,
"parentPostUrl": null
}
Optional values are null when Threads does not expose them; engagement counts are never invented. The OUTPUT key-value record summarizes every query as results, zero_results, blocked, or unknown. A genuine no-match page succeeds with zero rows.
Input recipes
Use these inputs as starting points in the Actor form or API:
- Brand mentions: Search your brand name with
sort: "recent"and a smallmaxItems. - Campaign comparison: Put two campaign phrases in
searchQueriesto collect both in one dataset. - Industry news: Combine a topic query,
sort: "recent", andsinceDateto follow recent discussion.
Performance and limits
Use focused terms and a realistic maxItems for faster monitoring. sinceDate filters posts whose timestamps are publicly visible; it cannot recover hidden timestamps. Threads can change anonymous search pages or show challenges, so the Actor reports blocked access rather than fabricating compatibility rows. Top and recent modes reflect what can be observed on the public search surface.
This Actor reads only anonymous public search pages. It does not accept cookies or credentials and does not collect private profiles, direct messages, full reply trees, Instagram data, or authenticated-only fields.
API and MCP
JavaScript API
const run = await client.actor('fetch_cat/threads-search-scraper').call({
searchQueries: ['climate tech'],
sort: 'recent',
maxItems: 100,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
You can also call fetch_cat/threads-search-scraper through the Apify API, schedules, webhooks, or the Apify MCP server using the same input fields.
Support and changes
If a public search result is parsed incorrectly, open an Actor issue with the query, run ID, and expected public field—never include cookies or credentials. See CHANGELOG.md for user-visible changes.
