Threads Scraper - Posts, Hashtags & Profiles
Under maintenancePricing
from $1.00 / 1,000 scraped posts
Threads Scraper - Posts, Hashtags & Profiles
Under maintenanceExtract posts from Threads by search query, hashtag or username. Returns post text, author username and display name, like, reply and repost counts, hashtags, media URLs, reply flag, timestamp and post URL. For social listening, brand monitoring and hashtag trend research on Meta's Threads.
Pricing
from $1.00 / 1,000 scraped posts
Rating
0.0
(0)
Developer
Ryan Zinburg
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
a day ago
Last modified
Categories
Share
Threads Scraper - Posts, Hashtags & Engagement
Extract posts from Threads, Meta's text network. Search a keyword or hashtag, or pull a specific profile's posts, and export each one with its engagement counts and attached media.
What you get per post
| Field | Example |
|---|---|
text | the post content |
authorUsername, authorDisplayName | who posted it |
likeCount, replyCount, repostCount | engagement |
hashtags | ["#ai", "#design"] |
mediaUrls | attached images and video |
isReply | whether it is a reply rather than a root post |
timestamp | when it was posted |
postId, postUrl | identifier and link |
Search filters
- searchQuery - keyword or hashtag, e.g.
#ai,product launch - username - a specific profile whose posts to collect
- sortBy - result ordering
- maxResults - how many posts to save
Example input
Use cases
- Brand monitoring - catch mentions of your product or campaign
- Hashtag and campaign tracking - measure reach and engagement around a tag over time
- Influencer discovery - find accounts in a niche whose posts actually get replies, not just likes
- Competitive intelligence - see what competitors publish and how the audience reacts
- Content research - study which formats and hooks perform in your category
- Trend analysis - track topic volume day by day
Notes on reliability
Threads has no public data API and actively rate-limits automated access. Expect the following:
- Use Apify Proxy for anything beyond small runs. Residential proxies give markedly better success rates than datacenter addresses.
- Result volume per query can vary between runs because the platform serves different slices of the feed.
- Engagement counts are snapshots; a post collected an hour after publication will show different numbers than the same post a day later.
- Media URLs are time-limited CDN links. Download what you need promptly rather than storing the URL for later.
Notes
isReplylets you separate original posts from conversation, which matters when measuring engagement rates.- Collect only public posts and use the data in line with Threads' terms and applicable privacy law; posts by identifiable people are personal data in the EU.
