Threads Scraper: Profiles, Posts, Views and Likes
Collect public Threads profiles and posts: text, views, likes, replies, reposts, media, hashtags, links, date, plus followers, bio and verified flag. Date filter and new-post monitoring. No login.
Who it is for
Marketers, creator-economy analysts, and researchers tracking public content and engagement over time.
Pricing
| Event | Price | Per 1,000 |
|---|---|---|
| ResultCharged once per Threads post (or profile row) delivered to the dataset, with view counts, likes, replies and the full profile block. Missing accounts, date-filtered posts and posts already delivered in monitor mode are never charged. | - | - |
| Actor StartCharged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). | $0.00005 | - |
Scheduled change: from Dec 5, 2026 the main event is -. Prices are read live from the Apify listing at build time.
Input
usernames· Usernames: Threads usernames (zuck), @handles or profile links (threads.com/@zuck). One per line.startUrls· Profile URLs: Same as Usernames, in URL-list form. Profile links like https://www.threads.com/@zuck.maxPosts· Max posts per profile: How many posts to return from each profile, newest first. Profiles with fewer posts return what exists.oldestPostDate· Only posts newer than: A date (2025-01-31) or a relative period (24 hours, 7 days, 2 weeks, 3 months, 1 year). Older posts are skipped and not charged. Pinned posts are always kept.includeViewCounts· Add view counts: On (default): opens each post page to read its view count (one extra request per post, run in parallel). Off: faster, view count left empty. Same price.maxConcurrency· Parallel post pages: How many post pages to load at once for view counts.monitorMode· Monitor mode: only new posts: Remembers posts delivered by earlier runs (in a named key-value store) and only returns and charges new ones. Ideal for schedules.stateStoreName· Monitor store name: Use a different name per schedule if you monitor different profiles.directFirst· Try a direct connection first: On by default: the run starts without a proxy (fastest) and switches to the proxy below, then to residential, only if Threads blocks or times out. Turn off to always use the proxy.autoProxyFallback· Switch to residential proxy when blocked: On by default: if Threads starts rate-limiting the datacenter IP, the run switches itself to Apify residential proxy instead of returning errors. Residential traffic is billed by Apify separately.
Use it from an AI agent (MCP)
Add this server URL to Claude, Cursor, VS Code or any MCP client. Authenticate with your Apify account.
https://mcp.apify.com/?tools=transparent_meteorite/threads-profile-scraper
FAQ
How do I run Threads Scraper: Profiles, Posts, Views and Likes?
Open it on Apify, fill in the input form, and press Start. You can also call it from the Apify API, a schedule, or an AI agent via MCP. Results land in a dataset you can download as JSON, CSV or Excel.
How is it billed?
Pay-per-event on Apify: you are charged only for the events listed in the price table above, plus nothing else from this listing. There is no subscription.
Where does the data come from?
Only publicly available sources. The Actor does not log in to any account or bypass access controls.
Can I use it from an AI assistant?
Yes. Add the MCP URL shown above to any MCP-capable client (Claude, Cursor, VS Code and others) and the Actor becomes a callable tool.