Threads Posts & Follower Count Scraper - Likes, Replies, Search

For brand monitoring, influencer research and competitor tracking: get Threads posts from any public account, keyword or post URL with each post's likes, replies, reposts, quotes, images and videos, plus the exact follower count, bio and verified badge of every account. Export the table as CSV, Excel or JSON, or read it through the API. No login, no cookies, no API key.

Keyword results come back clean: keep only posts that contain your keyword (on by default), only posts in your language (en, ja, es...) and only posts above a minimum number of likes. Posts left out by these filters are never charged.

What you can use it for

• Brand and mention monitoring: schedule your brand and product keywords with Monitoring mode on and receive only posts you have not seen before.
• Influencer research: exact follower count, bio, verified badge and the likes, replies and reposts of recent posts for every creator on your list.
• Competitor tracking: put competitor accounts side by side and compare engagement post by post.
• Follower history: schedule a daily run with Maximum posts per account set to 0, and each run adds one exact follower count per account.
• Research and AI datasets: post text, posted time and detected language, one row per post, ready for sentiment analysis or a RAG pipeline.

What you get

Input	Rows returned
Account (zuck, @zuck or a profile URL)	1 profile row (exact follower count, name, bio, bio links, verified badge, profile picture) + the newest posts
Keyword (coffee, machine learning)	The top posts Threads shows for it, filtered by keyword, language and likes
Post URL	That post with its current like, reply, repost and quote counts

Every post row has: post URL and code, text, posted time (UTC), like / reply / repost / quote / share counts, media type, image URLs, video URLs, link preview, topic tag, author username, name, verified badge and ID, whether it is a reply or pinned, quoted and reposted post links, and the detected language.

Why use this Threads scraper

• Exact follower counts, not rounded "5.7M" text (@zuck: 5,744,563 on 2026-10-13). Run it daily and you have a follower history for any public account.
• Relevant keyword results. Threads search mixes in replies and context posts that never mention your word. With Only posts that contain the keyword (on by default) those are left out and not charged.
• Language filter and minimum likes, so an English keyword gives you English posts with real engagement instead of a pile of zero-like posts in other languages. In a run on 2026-10-12, the keyword coffee with English selected returned 12 posts and left out 5 that were not in English or did not contain the word, at no charge.
• Monitoring mode returns only posts you have not received before, for brand, competitor and creator tracking on a schedule.
• Low start fee, and posts left out by your filters cost nothing. Empty results and accounts that need a login come back as free rows that say why.

How to use

1. Put accounts in Threads accounts, keywords in Search keywords, or links in Post URLs (any mix).
2. Set Maximum posts per account (0 = profile row only, for follower tracking).
3. Optional: Languages, Minimum likes, Posted on or after.
4. Run. Export the table as CSV, Excel or JSON, or read it through the API.

For daily follower tracking, schedule a run with your accounts and maxPostsPerAccount: 0. For new-post alerts, turn on Monitoring mode and schedule it.

Input fields

Field	What it does
usernames	Threads accounts (zuck, @zuck or profile URL)
searchQueries	Keywords to search Threads for
postUrls	Threads post links (threads.com or threads.net)
maxPostsPerAccount	Newest posts per account (default 30, 0 = profile row only)
maxPostsPerQuery	Posts per keyword (default 20)
includeProfile	One profile row per account with the exact follower count (default on)
onlyPostsContainingQuery	Keep only keyword results whose text contains the keyword (default on)
languages	Keep only posts in these languages (en, ja, es...)
minLikes	Keep only posts with at least this many likes
postedAfter	Keep only posts created on or after this date (UTC)
monitoringMode	Return only posts not returned by earlier runs
resetMonitoringState	Forget what was returned for these inputs

Example input

{
  "usernames": ["zuck", "@nasa"],
  "searchQueries": ["coffee"],
  "maxPostsPerAccount": 30,
  "languages": ["en"],
  "minLikes": 10
}

Example post row

{
  "type": "post",
  "inputType": "account",
  "input": "zuck",
  "postUrl": "https://www.threads.com/@zuck/post/DeZtp-TkQHh",
  "text": "Introducing ...",
  "postedAt": "2026-10-12T16:56:29.000Z",
  "likeCount": 973,
  "replyCount": 149,
  "repostCount": 75,
  "quoteCount": 36,
  "mediaType": "image",
  "imageUrls": ["https://scontent-...cdninstagram.com/..."],
  "authorUsername": "zuck",
  "authorIsVerified": true,
  "detectedLanguage": "en"
}

Example profile row

{
  "type": "profile",
  "username": "zuck",
  "fullName": "Mark Zuckerberg",
  "followerCount": 5744558,
  "isVerified": true,
  "biography": "...",
  "bioLinks": []
}

Pricing

Pay per event: a small fee per run start, a price per post row (post-returned) and the same price per profile row (profile-returned). In monitoring mode, each account, keyword or post URL that is read also costs a small check fee (target-checked), with or without new posts. Posts left out by your filters, and free rows (empty results, accounts that need a login, invalid input), are never charged. Set a maximum total charge on the run to cap the cost; the run stops cleanly at that limit and says so.

FAQ

How do I search Threads posts by keyword in one language? Add the keyword in Search keywords and your language code in Languages (for example en). Keep Only posts that contain the keyword on to drop unrelated replies.

Why does a Threads keyword search give me posts in other languages or with no likes? Threads mixes replies and posts in many languages into keyword results. Set Languages (for example en) and Minimum likes, and keep Only posts that contain the keyword on. Posts that do not pass are left out and not charged.

How do I get the follower count of a Threads account every day? Add the usernames, set Maximum posts per account to 0, and schedule the Actor daily. Each run returns one profile row per account with the exact followerCount.

Can I export Threads posts to CSV or Excel? Yes. Download the run's table as CSV, Excel or JSON from the Output tab, or read it through the Apify API.

How do I scrape all posts from a Threads profile? Add the username and raise Maximum posts per account. The Actor pages through the account's posts newest first, as far as Threads shows them to visitors who are not logged in (about the newest 150 threads).

Can I get only new posts since the last run? Yes. Turn on Monitoring mode and schedule the Actor. Later runs return only posts not returned before for each account and keyword.

Do I need a Threads account or cookies? No. The Actor reads public Threads pages without logging in.

Good to know

• Threads shows visitors who are not logged in about the newest 150 threads of an account, and about the top 20 posts for a keyword (no "recent" tab without login). Use several related keywords to collect more.
• Some accounts (and names that do not exist) send visitors to the Threads login page. These come back as a free not-available-without-login row; this Actor never logs in.
• detectedLanguage is estimated from the post text, so it can be wrong on short or mixed-language posts. Very short posts get null and are left out when Languages is set.
• Image and video URLs are signed Threads CDN links and expire after some days; download the files if you need them later.
• A post returned for one input is not returned (or charged) a second time in the same run.
• Email addresses and phone numbers in bios and post text are masked.

Thanks for using this Actor

We build these tools for people who run them every day, and we improve them from what users tell us.

• Missing a field, or need another filter? Tell us in the Issues tab. If the data is there, we add it.
• Found a bug or a wrong value? Post the run ID in the Issues tab. Wrong data is the thing we fix first.

If this Actor saved you time, a short review helps other people find it.