Threads Search & Monitor — Keyword Tracking + Contacts

Search Threads by keyword or hashtag, monitor saved searches for new posts on a schedule, and optionally pull full reply trees and author bio contacts (email/phone) — all in one actor. Cookie-free, no login, no tokens to maintain. Runs on the Apify platform; export to JSON, CSV, or Excel, or pull straight from the API.

It's the only Threads search actor on the Store with a dedup-aware monitor mode: schedule it and every run returns only the posts it hasn't seen before.

---

What does Threads Search & Monitor do?

Give it one or more keywords or hashtags and it returns the matching public Threads posts — author, text, engagement counts (likes / replies / reposts / quotes), media URLs, timestamp, and a deep link to each post. Three modes:

• Search — keyword / phrase query, gathered across Threads' relevance and recency views for wider coverage per term.
• Hashtag — tag feeds, same wide-coverage gathering.
• Monitor — re-run your saved searches/hashtags on a schedule and get only the new posts since the last run (dedup-aware, persisted across runs).

Two optional enrichments no other Threads search actor bundles:

• Reply trees on results — pull the top discussion replies under each surfaced post (depth-aware).
• Author bio contacts — resolve email / phone / links from each unique author's bio (great for lead-gen), deduped so you're charged once per author.

Why use Threads Search & Monitor?

• Social listening teams & agencies — track brand, competitor, and topic keywords now that Threads has opened ads to all advertisers and crossed 450M+ monthly users. Schedule the monitor and never re-pull the same post.
• Market & trend researchers — gather the relevance + recency union per term, filter by date, export clean structured rows.
• Lead-gen & outreach — find posts on your topic, then resolve the authors' bio contacts in the same run.
• AI / dataset builders — collect topical public posts (and their discussions) as clean JSON for training and retrieval.
• No maintenance moat — uses Meta's public social-bot SSR, so there are no rotating doc_ids, login cookies, or tokens to break. Reliable by design.

How to use Threads Search & Monitor

1. Click Try for free / Start.
2. Pick a Mode (Search, Hashtag, or Monitor).
3. Enter your search queries and/or hashtags.
4. (Optional) Turn on Include reply trees and/or Resolve author bio contacts; set a date window and Max items.
5. For hands-off monitoring: set Mode = Monitor, then attach an Apify Schedule (e.g. hourly/daily). Each run appends only new posts.
6. Run it, then export the dataset as JSON / CSV / Excel, or read it from the API.

Input

Search a keyword (wide coverage):

{
  "mode": "search",
  "searchQueries": ["threads api", "social listening"],
  "sort": "top",
  "maxResultsPerQuery": 50
}

Monitor hashtags on a schedule (only new posts each run):

{
  "mode": "monitor",
  "hashtags": ["bitcoin", "ai"],
  "maxResultsPerQuery": 50
}

Search + reply trees + author contacts (lead-gen):

{
  "mode": "search",
  "searchQueries": ["dtc brand"],
  "includeReplies": true,
  "maxReplyDepth": 2,
  "resolveContacts": true,
  "resolveLinktree": true,
  "maxItems": 300
}

Search a date window:

{
  "mode": "search",
  "searchQueries": ["world cup"],
  "dateFrom": "2026-05-01",
  "dateTo": "2026-06-01"
}

Output

One post row (replies and author-contact rows share the same dataset, distinguished by recordType):

{
  "recordType": "post",
  "matchedQuery": "threads api",
  "postId": "3904856121039465368",
  "code": "DZFe09QgoGI",
  "url": "https://www.threads.com/@example/post/DZFe09QgoGI",
  "username": "example",
  "fullName": "Example User",
  "text": "Shipping a new Threads integration today…",
  "takenAt": "2026-06-12T14:23:51.000Z",
  "likeCount": 412,
  "replyCount": 37,
  "repostCount": 8,
  "quoteCount": 3,
  "mediaType": "image",
  "mediaUrls": ["https://…"],
  "serpTypes": ["default", "recent"],
  "fetchedAt": "2026-06-13T09:00:00.000Z",
  "sourceUrl": "https://www.threads.com/search?q=threads%20api&serp_type=default"
}

Reply row (recordType: "reply"): adds depth, parentPostId, replyToAuthor. Author row (recordType: "author", when resolveContacts is on): biography, followerCount, isVerified, bioLinks, extractedEmails, extractedPhones, matchedQueries.

Field	Description
recordType	post | reply | author
matchedQuery	Which search keyword / hashtag surfaced this row
serpTypes	Which view(s) the post appeared in (default = relevance, recent = newest)
username / fullName	Author identity
text	Post body
takenAt	Post timestamp (ISO)
likeCount / replyCount / repostCount / quoteCount	Engagement
mediaType / mediaUrls	text | image | carousel | video + best-resolution URLs
depth / parentPostId / replyToAuthor	Reply linkage (reply rows)
extractedEmails / extractedPhones / bioLinks	Author contacts (author rows)
url	Canonical deep link to the post

How much does it cost to scrape Threads?

Pay-per-event — you pay for what you pull:

Event	Price	When it fires
Search result	$0.0025	Per post surfaced for a query/hashtag (primary)
Reply fetched	$0.0015	Per reply, only when Include reply trees is on
Monitor delta detected	$0.005	Per new post in monitor mode
Author bio contact resolved	$0.02	Once per unique author, only when Resolve contacts is on

The first 10 chargeable events of every run are free — try it on a real query before paying.

Typical runs:

• 50 search results: ~$0.13 (under $2.50 / 1,000 posts — cheaper than every comparable Threads search actor).
• 50 results + their reply trees (~15 replies each): ~$0.13 + ~$1.10 replies.
• Monitor 5 hashtags, ~20 new posts/run: ~$0.10 per scheduled run.
• 30 results + contacts on 25 unique authors: ~$0.075 + ~$0.50 contacts.

Tips & advanced options

• Coverage is honest, not infinite. Threads' public (cookie-free) search exposes a bounded sample per term — typically a few dozen posts. This actor widens it by unioning the relevance and recency views (deepCoverage, on by default), but there is no deep cursor pagination on the public path; maxResultsPerQuery caps what the union exposes. For broader sweeps, run several related queries.
• Monitor is the hands-off mode. Set Mode = Monitor + an Apify Schedule. Dedup is code-based and persisted in a named store, so you never re-pull or re-pay for a post you already got. For very high-volume terms, an early run may surface a fresh slice each time as Threads rotates its public sample; it settles as the seen-set fills.
• Reply trees return the top replies embedded in each post's page (depth-aware via reply-to-author). A post with thousands of replies returns its top discussion sample, not every reply.
• Contacts: turn on resolveLinktree to follow Linktree / Beacons / Stan links for extra channels. Author rows are deduped — one per author per run.
• Use a residential proxy (default) for reliability — Meta intermittently per-IP-gates social-bot fetches; rotation handles it. Datacenter works for tiny runs.
• Date window (dateFrom / dateTo) filters the gathered set; it does not fetch posts older than Threads exposes.

Legal & responsible use

This actor collects only public Threads data available without logging in, via Meta's public social-bot rendering. It does not bypass authentication or access private/age-gated content. You are responsible for using the output in compliance with Threads'/Meta's Terms, the Apify Terms of Service, and applicable data-protection law (GDPR/CCPA) — especially for the contact-extraction feature, where you must have a lawful basis for processing personal data. No personal data is stored by the actor beyond the dataset it returns to you.

FAQ & support

Why can't I get thousands of posts for one keyword? Threads' public search has no cursor pagination without logging in. We widen coverage by unioning the relevance + recency views (a few dozen posts/term) and let you run many queries. We deliberately stay cookie-free for reliability rather than chase a login-gated pagination path.

How is this different from the generalist Threads scrapers? This one is built for search & monitoring: multi-view coverage per term, a dedup-aware scheduled monitor, and reply + contact enrichment on search results — none of which the keyword-only incumbents bundle.

Does monitor mode re-charge me for the same post? No. Dedup is persisted across runs in a named key-value store; you're only charged for posts you haven't seen.

Do I need a Threads/Meta account or API key? No. No login, no cookies, no tokens.

Why did a query return nothing? The term may have no public posts, or Meta gated that IP on the attempt — enable the residential proxy (default) and retry.

Support: open an issue on the actor's Issues tab. Bugs and feature requests welcome.