Threads Search Scraper - Posts by Keyword & Hashtag, No Login
Pricing
from $1.50 / 1,000 results
Threads Search Scraper - Posts by Keyword & Hashtag, No Login
Search Threads posts by keyword or #hashtag without logging in: text, author, likes, replies, reposts, views, media, links and date. Top or newest first, 60-85 posts per keyword, filters for likes, replies, language and date. From $1.50 per 1,000 posts.
Pricing
from $1.50 / 1,000 results
Rating
0.0
(0)
Developer
Alom Dev
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Threads Search Scraper: Posts by Keyword & Hashtag, No Login
Search Threads posts by keyword or #hashtag and get them as a table: one row per post with the text, author, likes, replies, reposts, view count, media, links, language and date. Top posts or newest first, with filters so you keep only the posts worth reading.
- No login needed. It reads what a logged-out visitor of threads.com sees. No account of yours is involved.
- 60-85 posts per keyword, not 20. Threads shows logged-out visitors one page of about 20 results. This Actor opens several result pages (keyword search, tag search, the tag page) from fresh IPs and merges them.
- Filters: minimum likes, minimum replies, language and date window. Posts that don't pass are not charged.
- View counts ("423K views") on request, and a guessed
languageon every post. - Only new posts on a schedule. Monitoring mode skips posts an earlier run returned, and you don't pay for them.
- Export to CSV, Excel or JSON, or pull results through the Apify API, Make, Zapier or n8n.
This Actor is a focused version of the Threads Scraper (same code, same prices). Use the Threads Scraper if you also need profiles, a profile's posts or the replies under a post.
What can you use it for?
- Brand and product mentions: what people write about your brand, product or competitor.
- Hashtag research: the top posts and the newest posts for a #hashtag, with engagement counts.
- Trend and content research: which posts on a topic get the likes and views.
- Social listening for AI agents: a clean, filtered feed for Claude, ChatGPT or Cursor through MCP (below).
Input
| Field | What it does |
|---|---|
searchQueries | Keywords, #hashtags, or threads.com search / /tag/ URLs. |
searchSort | top (Threads' order, default) or recent (newest first). |
maxPosts | Max posts per keyword. Default 50. |
requireKeywordMatch | Keep only posts whose text, topic tag or link title contains the keyword. Default off. |
postedAfter / postedBefore | Date window, e.g. 2026-10-01 or 7 days. |
minLikes / minReplies | Keep only posts with at least this many likes / replies. |
languages | Keep only posts in these languages, e.g. ["en"]. Posts too short to tell are kept. |
includeViews | Fill viewCount on every post. One extra request per post, about 1.5 s each, not charged. Default off. |
onlyNewSinceLastRun + monitorName | Skip posts an earlier run with the same monitor name returned. |
sessionCookie | Optional, never required: your own logged-in cookie unlocks Threads' real Recent tab with deep paging. At your own risk. |
{ "searchQueries": ["espresso machine", "#coffee"], "maxPosts": 50 }
{ "searchQueries": ["ai agents"], "searchSort": "recent", "minLikes": 10, "languages": ["en"], "includeViews": true }
{ "searchQueries": ["yourbrand", "#yourbrand"], "searchSort": "recent", "onlyNewSinceLastRun": true, "monitorName": "brand" }
Switching from another Threads search scraper?
Keep your input. These field names are accepted as they are: searchQuery (one keyword) or keywords (a list),
sort (top / recent), sortByRecent (true / false), after / before (dates) and maxItemsPerKeyword.
Output example
{"type": "post","postId": "3741234567890123456","code": "DdXmpl3ExAm","url": "https://www.threads.com/@example_cafe/post/DdXmpl3ExAm","text": "Finally dialed in the new espresso machine. 18g in, 36g out, 28 seconds ☕","username": "example_cafe","fullName": "Example Cafe","isVerified": false,"likeCount": 312,"replyCount": 41,"repostCount": 6,"quoteCount": 2,"viewCount": 18430,"mediaType": "image","media": [{ "type": "image", "url": "https://scontent…jpg", "width": 1440, "height": 1800 }],"hashtags": [],"topicTag": "Coffee Threads","language": "en","keywordMatch": true,"searchKeyword": "espresso machine","date": "2026-10-14T08:12:40.000Z","source": "search:espresso machine","scrapedAt": "2026-10-16T09:00:00.000Z"}
(The post above is made up; the fields are what you get.) Every post also has urls, mentions, linkPreview,
quotedPost, isReply, isPaidPartnership, isAiGenerated and more; see the
Threads Scraper for the full list. viewCount is null unless
includeViews is on. Values Threads doesn't show are null, never a made-up 0.
How much does it cost?
The same prices as the Threads Scraper: from $1.50 per 1,000 posts, plus $0.005 per run. Platform usage (compute, proxy) is included.
| Apify plan | Price per 1,000 posts |
|---|---|
| Free | $2.50 |
| Starter (Bronze) | $2.00 |
| Scale (Silver) | $1.75 |
| Business (Gold) and above | $1.50 |
Two keywords x 50 posts cost $0.25 on the Free plan. You pay only for rows you receive: posts removed by your filters and posts a monitor already returned are free.
Monitoring (only new posts)
Turn on "Only new posts since my last run", give it a name (e.g. brand), set the order to Recent and
schedule the run in Apify Console. Each run returns only posts you haven't received yet. For a monitor with these
settings already on, see the Threads Hashtag & Keyword Monitor.
Use it from AI agents (Claude, ChatGPT, Cursor and other MCP clients)
Add https://mcp.apify.com/?tools=alom/threads-search-scraper as a connector (Claude: Settings → Connectors → Add
custom connector; Claude Code: claude mcp add --transport http threads-search "https://mcp.apify.com/?tools=alom/threads-search-scraper")
and sign in with your Apify account. Then ask, for example: "Find English posts about espresso machines from this
week with at least 10 likes and summarise the complaints." Keep maxPosts at 10-30 so the answer fits the context.
Limitations
- About 60-85 posts per keyword without login. That is what several logged-out result pages add up to, not every post ever written. With your own session cookie the Recent tab pages much deeper (300 recent posts for "news" in our test, versus 155 without).
- "Recent" without a cookie sorts the posts found newest first; it is not Threads' own Recent tab.
- Threads' search is loose: it also returns related posts that don't contain the keyword. Every row has
keywordMatch; turn onrequireKeywordMatchto drop them. - View counts add about 1.5 s per post and are missing on some small, new posts (33 of 40 search posts had one in our test).
FAQ
Do I need a Threads or Instagram account? No. Nothing is logged in by default, so there is nothing to ban.
Can I search for posts from one account? Use the Threads Scraper with the username: it pages through the account's posts, which is more complete than search.
Is it legal? The Actor collects only what Threads shows publicly without login. Posts are personal data: check that your use has a lawful basis (GDPR and similar laws) before you store or process them.
More scrapers from the same developer
- Threads Scraper: posts, profiles, replies, reposts, keyword and hashtag search, account search
- Threads Profile Scraper: followers, bio, bio links and contacts of any Threads account
- Threads Replies Scraper: the replies under any Threads post with whole reply threads
- Threads Hashtag & Keyword Monitor: only the new posts for your keywords and #hashtags, for scheduled runs
- Threads Account Finder: Threads accounts by keyword with followers, bio links and the contacts they list
- Google Trends API & Scraper: interest over time, regions, related queries and Trending Now
- YouTube Scraper: videos, channels, Shorts, comments, subtitles and community posts without the API quota
Feedback
Missing a field, found a bug, or need a feature? Open an issue in the Issues tab and I'll take a look. If this Actor saved you time, a short review on the Store page helps other people find it.