Threads Search Scraper - Keywords, Tags & Profiles

Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc. or any of its subsidiaries. All trademarks mentioned are the property of their respective owners. "Threads" is referenced only to describe the publicly available website this Actor collects data from.

Search Threads by keyword or hashtag and get the posts back as clean, structured rows - text, engagement counts, media, author identity and timestamps. Also pulls any public profile's recent timeline. No login, no cookies, no session token.

Built for social listening, brand monitoring, competitor tracking and content research on the network that is still cheap to monitor.

---

What you get

One row per post, every row carrying the same 28 fields:

Field	What it is
postUrl, postCode, postId	Canonical link and IDs
text, textLength	Full post text
username, userFullName, userId	Author identity
userIsVerified	Verified badge, true/false
userProfileUrl, userProfilePicUrl	Author links
likeCount, replyCount, repostCount, quoteCount	Engagement
engagementTotal	The four counts summed - sort on this
publishedAt	ISO 8601 timestamp
isReply, isQuotePost	Post kind, true/false
hashtags, mentions	Parsed from the text
imageUrl, videoUrl, hasMedia	Attached media
sourceType, sourceQuery	Which keyword/tag/profile found it
scrapedAt	When this row was collected

Every record carries every field, so your CSV never has ragged columns.

Search modes - combine as many as you like in one run

• Keywords - ["supabase", "claude code"] searches Threads' post index
• Hashtags - ["ai", "startup"] searches the tag feed
• Usernames - ["zuck", "mosseri"] pulls those profiles' recent posts

Filters

minLikes · onlyWithMedia · excludeReplies · maxPerSource · maxResults

Filters run inside the crawl, so a filtered-out post never costs you anything.

---

Example input

{
  "keywords": ["supabase"],
  "hashtags": ["ai"],
  "maxResults": 100,
  "minLikes": 10,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Example output

{
  "type": "post",
  "postUrl": "https://www.threads.com/@user/post/DMxxxxxxx",
  "text": "We just shipped realtime presence...",
  "username": "user",
  "userFullName": "A Name",
  "userIsVerified": false,
  "likeCount": 412,
  "replyCount": 33,
  "repostCount": 12,
  "quoteCount": 2,
  "engagementTotal": 459,
  "publishedAt": "2026-08-05T14:21:03.000Z",
  "isReply": false,
  "hashtags": ["supabase"],
  "hasMedia": true,
  "imageUrl": "https://...",
  "sourceType": "keyword",
  "sourceQuery": "supabase"
}

---

Pricing

$0.003 per post. You are charged only for rows actually delivered to your dataset.

A run that finds nothing - a nonsense keyword, or filters that exclude everything - costs $0 and tells you why in the run status message.

Honest limits

Please read these before buying; they are properties of Threads, not bugs:

• Threads serves logged-out visitors one page of recent results per search. This actor is built for monitoring (run it on a schedule and accumulate) rather than deep historical backfill. A single run returns roughly 10-25 posts per keyword.
• Hashtags and mentions are sparse because Threads is a text-first network - measured on a real 134-post sample, only 8 posts carried a hashtag and 1 carried an @mention. The parser extracts every one that exists.
• Media is optional: about 37% of posts carry an image and 11% a video.
• Use the residential proxy (the default). Threads throttles per IP.

Automate & schedule

Run this Actor on autopilot and pull results into your own stack:

• Apify API - start runs, fetch datasets and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python - official SDKs.
• Schedules - run it hourly, daily or weekly and keep your dataset current.
• Webhooks - trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/threads-search-scraper').call({
    "keywords": [
        "supabase"
    ],
    "hashtags": [],
    "usernames": [],
    "maxResults": 100,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} records`);

Integrate with any app

Connect the dataset to thousands of apps - no code required:

• Make - multi-step automation scenarios.
• Zapier - push new records straight into your CRM or spreadsheet.
• Slack - get notified when a scheduled run finds something new.
• Google Drive / Sheets - auto-export every run to a spreadsheet.
• Airbyte - pipe results into your data warehouse.
• GitHub - trigger runs from commits or releases.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. You can call this Actor from Claude, ChatGPT or any agent framework through the Apify MCP server - describe the data you need and let the assistant run this Actor for you.

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready — AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

• x402 — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server — no account, no API key.
• Skyfire — agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

FAQ

How is this Actor billed? Pay-per-event: you pay only for the results it delivers, with no monthly rental and no start fee. The per-event price is shown on the Pricing tab.

Can I schedule it and get results automatically? Yes - create a Schedule and add a webhook or an integration (Google Sheets, Slack, Make, Zapier) to push each run's dataset wherever you need it.

Which export formats are available? Every run's dataset can be downloaded as JSON, CSV, Excel (XLSX), XML, HTML or RSS from the Apify Console or the API.

Can I run it from code or an AI agent? Yes - through the Apify API and client libraries, or from Claude, ChatGPT and other assistants via the Apify MCP server.

Is it legal to scrape Threads? This Actor collects publicly available data only. You are responsible for using the output in compliance with applicable laws (including data-protection law where personal data is involved) and the source's terms. See Data & lawful use and the Disclaimer below.

Is this an official Threads tool? No. It is an independent, third-party Actor with no affiliation to, endorsement by or sponsorship from Meta Platforms, Inc. See the Disclaimer below.

Tips

• Schedule it. The value is in the time series - run hourly or daily on your brand terms and let the dataset build.
• Sort by engagementTotal to find what actually landed.
• sourceQuery tells you which of your terms surfaced each post, so you can run 10 keywords in one job and still attribute them.

Related actors

• Instagram Profile Scraper - bulk bio and follower stats
• Instagram Leads Scraper - emails and contacts from IG profiles
• Facebook Reels Scraper - Reels with play counts

Data & lawful use

This Actor reads only what Threads publishes to logged-out visitors: it does not log in, use cookies or session tokens, create accounts, or reach anything behind a sign-in. Names, handles, bios and engagement figures are public, but they relate to identifiable people, so treat the output as personal data. If you are in the EU or UK you are the data controller for what you do with it: have a lawful basis (usually legitimate interest for research, marketing analytics or B2B prospecting), honour access and deletion requests, and do not use the output for spam or unsolicited messaging.

Under Apify's Standard Actor Contract, which governs your use of this Actor, you are the controller of any personal data in your input and output and scrapesage acts only as your processor: that data is processed solely to run your job, written only to your own Apify storage, never used for any other purpose and never shared onward. If you need help with a data-subject request that involves this Actor's output, open an issue on the Issues tab.

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc. or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.

"Threads" and any related marks are the property of their respective owners and are used here only in a descriptive, nominative sense - to identify the publicly accessible website from which this Actor collects data. This Actor is not an official Threads product, is not authorised or certified by Meta Platforms, Inc., and does not distribute Threads software. It collects only publicly available information; you are responsible for ensuring your use of that data complies with applicable laws, regulations and the terms of the source website.

Need help?

Open an issue on the Actor's Issues tab, or visit the Apify help center. Feature requests are welcome - this Actor is actively maintained.