Threads Hashtag & Keyword Monitor

Track Threads keywords and #hashtags on a schedule, without logging in. Every run returns only posts you haven't received yet, newest first, with text, author, likes, replies, reposts, media and the post URL.

• Only new posts: posts an earlier run delivered are skipped and not charged. On by default.
• Only posts that contain the keyword (on by default): Threads' logged-out search also returns unrelated new posts, and this filter drops them (not charged).
• Newest first, with optional filters for likes, replies, language and date.
• No login needed. An own session cookie is optional.
• $2.50 per 1,000 posts on the Free plan, $1.50 on Business, plus $0.005 per run.

How to monitor Threads in 3 steps

1. Enter your keywords or #hashtags (e.g. your brand, a competitor, a campaign hashtag).
2. Press Start once. The first run returns the latest matching posts.
3. Add a Schedule (e.g. every hour). Each run then returns only new posts. Send them to Slack, Google Sheets or e-mail through Apify integrations, Make, Zapier or n8n.

The Free plan's $5 monthly credit covers about 2,000 posts, so you can try it on your real keywords first.

How to set up a monitor

1. Add your keywords and hashtags, e.g. #yourbrand, your brand, competitor name.
2. Leave Only new posts since my last run on and pick a Monitor name (or keep default).
3. Save it as a Task and add a Schedule in Apify Console (every hour, every morning...).
4. Optional: add an integration (Slack, webhook, Google Sheets) to get each run's new posts.

The first run returns what Threads shows now; the next runs return only what is new since then.

Input

Field	What it does
searchQueries	Keywords, #hashtags, or threads.com search / /tag/ URLs.
searchSort	recent (default, newest first) or top.
requireKeywordMatch	Only posts whose text, topic tag or link title contain the keyword (the rest are not charged). Default on.
onlyNewSinceLastRun	Only posts no earlier run with the same monitor name returned. Default on.
monitorName	Monitor name. Each name has its own memory. Default default.
maxPosts	Max posts per keyword per run. Default 50.
postedAfter	Skip older posts: a date, ISO timestamp or 7 days.
minLikes, minReplies	Keep only posts with at least this many likes / replies. Cuts the posts nobody reacted to.
languages	Keep only posts in these languages, e.g. ["en"]. The language is guessed from the text (see language on each row); posts too short to tell are kept.
includeViews	Fill viewCount (the number behind "423K views") on every post. One extra request per post, about 1.5 s each, not charged. Default off.
sessionCookie	Optional, your own logged-in cookie (see below).

{ "searchQueries": ["#coffee", "espresso machine"], "monitorName": "coffee-brand" }

The field names are the same as in the Threads Scraper, so an input works in both.

Output example

{
    "type": "post",
    "postId": "3994109866205639942",
    "code": "Ddt7cL5EfUG",
    "url": "https://www.threads.com/@someuser/post/Ddt7cL5EfUG",
    "text": "Finally dialed in my new espresso machine ☕",
    "username": "someuser",
    "fullName": "Some User",
    "isVerified": false,
    "likeCount": 42,
    "replyCount": 7,
    "repostCount": 1,
    "quoteCount": 0,
    "mediaType": "image",
    "media": [{ "type": "image", "url": "https://scontent…webp", "width": 1440, "height": 1800 }],
    "hashtags": [],
    "topicTag": "Coffee",
    "mentions": [],
    "urls": [],
    "isReply": false,
    "timestamp": 1790355021,
    "date": "2026-09-25T16:50:21.000Z",
    "searchKeyword": "espresso machine",
    "keywordMatch": true,
    "source": "search:espresso machine",
    "scrapedAt": "2026-09-25T17:02:10.000Z"
}

Posts carry the same fields as in the Threads Scraper (quoted post, link preview, mentioned accounts, AI label and more). Values Threads doesn't show are null, never 0. Each keyword's posts come newest first; with several keywords, their blocks can interleave.

How much does it cost?

Proposed: the same prices as the Threads Scraper, from $1.50 per 1,000 posts, plus $0.005 per run. One result = one post.

Apify plan	Price per 1,000 results
Free	$2.50
Starter (Bronze)	$2.00
Scale (Silver)	$1.75
Business (Gold) and above	$1.50

You pay only for posts you receive. Posts a monitor already delivered, posts filtered out by requireKeywordMatch or postedAfter, and duplicates are free. An hourly run that finds nothing new costs only the run fee. Platform usage (compute, proxy) is included.

Own session cookie (optional, at your own risk)

You never need it. If you paste the cookies of your own logged-in threads.com tab into sessionCookie (the Cookie header or a JSON export with at least sessionid), searches use Threads' real Recent tab and page through it like the app, which finds more recent posts per keyword. Requests are then made as your account (one IP, at most 2 in parallel). Meta may rate-limit, checkpoint or ban accounts that scrape: use a spare account, and you carry that risk. The cookie is stored encrypted as a secret input and never logged or written to the results. If Threads rejects it, the run says so in the log and continues logged out.

Limitations

• Logged-out search shows ~20 posts per result page and no "next page". Each run opens several result pages (keyword search, tag search, tag page) from fresh IPs and merges them: typically 60-85 unique posts per keyword per run. A busy hashtag can get more new posts per hour than that; schedule more often, or use your own cookie.
• Without a cookie Threads has no "Recent" tab for logged-out visitors, so "newest first" sorts the posts that were found. A post can show up a few runs late if Threads didn't show it earlier.
• With the keyword filter on, a rare keyword can return few or no posts in a run: that is the honest answer, not an error (the run ends as empty).
• Monitor memory keeps the last 200,000 delivered posts per monitor name.
• Not available without login: view counts, polls.

FAQ

Do I need a Threads or Instagram account? No. The cookie is optional.

How do I start a monitor from scratch? Use a new monitor name.

Is it legal? It collects publicly visible posts. You are responsible for how you use the data, including data protection rules for personal data (usernames, post text).

More scrapers from the same developer

• Threads Search Scraper: posts by keyword or #hashtag, top or newest first, with filters
• 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, or every reply an account wrote
• Threads Scraper: posts, profiles, replies, reposts, keyword and hashtag search, account search
• Google Trends API & Scraper: interest over time, regions, related queries and Trending Now, a pytrends alternative
• YouTube Scraper: videos, channels, Shorts, comments, subtitles and community posts without the API quota
• Bilibili Scraper: videos, creators, full comment threads and danmaku from B站, no login
• Google Hotels Scraper: hotel prices from every booking site across dates, room rates and reviews
• Google Ads Transparency Scraper: every Google ad a competitor runs, with the real ad copy
• Threads Account Finder: Threads accounts by keyword with followers, bio links and the contacts they list
• YouTube Comments Scraper: comments and replies of any YouTube video or Short
• YouTube Channel Scraper: every video of a channel with views, likes, dates and channel stats
• YouTube Shorts Scraper: Shorts by channel or keyword with views and likes
• Google Flights Scraper: flight prices, airlines, layovers and a cheapest-date calendar for any route

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.