Threads Scraper — Extract Posts, Profiles, and Search Results from Threads.net

Scrape Threads.net posts, user profiles, and search results at scale. Collect post text, engagement metrics (likes, replies, reposts, shares), profile data with follower counts, media URLs, and contact information. Process up to 20 requests in parallel with automatic retries and proxy rotation.

Pricing

Plan	Price	Best For	Link
Pay per result	$2 / 1,000 results	One-time scraping, small batches	Threads Scraper Usage
Monthly subscription	$20 / month	Regular monitoring, unlimited usage	Threads Scraper Monthly

Both plans have identical functionality — choose the one that fits your workflow.

Key Features

• Search posts by keyword — find Threads posts matching any search query, with full engagement data
• Scrape user profiles — extract bio, follower count, verification status, profile links, and contact info
• Scrape profile posts — get a user's recent posts along with their profile data
• Extract post replies — collect full reply threads for any specific post
• Parallel processing — up to 20 concurrent requests for maximum throughput
• Auto-retry with proxy rotation — 5 retry attempts per request, each with a fresh proxy IP
• Contact extraction — automatically finds emails and URLs in post text and user bios
• Multiple media types — handles text posts, photos, videos, and carousels with full media URLs
• Flexible input formats — accepts usernames, @usernames, or full profile/post URLs

What Data You Get

Search and post data

Field	Description
post_id	Unique post identifier
text	Full post text
taken_at	Unix timestamp
like_count	Number of likes
reply_count	Number of replies
repost_count	Number of reposts
quote_count	Number of quotes
reshare_count	Number of shares
username	Author username
full_name	Author display name
is_verified	Verified account flag
media_type	Content type: text (19), photo (1), video (2), carousel (8)
images	Array of image URLs with dimensions
video_versions	Video URLs (if video post)
carousel_media	Carousel items (if carousel post)
post_url	Direct link to the post
emails_in_text	Emails found in post text
urls_in_text	URLs found in post text
reply_control	Who can reply: everyone, accounts_you_follow, mentioned_only
is_reply	Whether this is a reply to another post

Profile data

Field	Description
user_id	Numeric user ID
username	Username
full_name	Display name
biography	Bio text
bio_fragments	Structured bio (mentions, hashtags, links)
bio_links	Links from bio
profile_pic_url	Avatar URL
hd_profile_pics	HD avatar versions
follower_count	Number of followers
is_verified	Verified account flag
is_private	Private account flag
emails_in_bio	Emails found in bio
urls_in_bio	URLs found in bio
posts	User's recent posts (when include_posts is enabled)

Post detail fields (additional)

Field	Description
replies	Array of replies to this post (same data structure)
quoted_post	Quoted post data
reposted_post	Reposted post data
link_preview	Link preview attachment
text_fragments	Structured text with mentions, hashtags, and links
is_paid_partnership	Paid partnership flag
is_pinned_to_profile	Pinned to profile flag

Use Cases

• Social media monitoring — track brand mentions, trending topics, and audience sentiment on Threads in real time
• Influencer research — find and evaluate Threads creators by follower count, engagement rate, and posting frequency for partnership decisions
• Content analysis — analyze post performance, identify top-performing content formats, and track engagement patterns across keywords
• Lead generation — extract contact information (emails, URLs) from Threads profiles and posts for outreach campaigns
• Market research — monitor competitor activity, product discussions, and industry trends on Meta's text-based platform

How It Works

1. Choose an action — search (find posts by keyword), profile (scrape user data), or post (get specific posts with replies)
2. Provide inputs — keywords for search, usernames for profiles, or post URLs
3. Actor processes in parallel — up to 20 concurrent requests with residential proxy rotation
4. Download results — structured JSON, CSV, or Excel from the Apify dataset

Input Parameters

Parameter	Type	Required	Description
action	String	Yes	search, profile, or post
queries	String[]	For search	List of search keywords
usernames	String[]	For profile	Usernames, @username, or full profile URLs
posts	String[]	For post	Full post URLs
include_posts	Boolean	No	Also scrape user's recent posts (for profile action)
serp_type	String	No	default (posts) or accounts (search for accounts)
proxy	Object	No	Proxy configuration (default: Residential US)

Input examples

Search posts:

{
    "action": "search",
    "queries": ["python programming", "javascript", "AI tools"]
}

Scrape profiles with posts:

{
    "action": "profile",
    "usernames": ["zuck", "@mosseri", "https://www.threads.net/@instagram"],
    "include_posts": true
}

Scrape specific posts with replies:

{
    "action": "post",
    "posts": [
        "https://www.threads.net/@zuck/post/DVrwsE5EdSz"
    ]
}

Output Example

Search result

{
    "post_id": "3578921456789012345",
    "code": "DVp9LrHAjHq",
    "text": "Just launched our new Python library for data processing...",
    "taken_at": 1710000000,
    "media_type": 19,
    "like_count": 245,
    "reply_count": 32,
    "repost_count": 18,
    "quote_count": 5,
    "reshare_count": 12,
    "username": "techdev",
    "full_name": "Tech Developer",
    "is_verified": true,
    "is_reply": false,
    "images": [],
    "post_url": "https://www.threads.net/@techdev/post/DVp9LrHAjHq",
    "emails_in_text": ["hello@techdev.com"],
    "urls_in_text": ["https://github.com/techdev/library"]
}

Profile result

{
    "user_id": 12345678901,
    "username": "zuck",
    "full_name": "Mark Zuckerberg",
    "biography": "Building the future of connection.",
    "profile_pic_url": "https://...",
    "follower_count": 12500000,
    "is_verified": true,
    "is_private": false,
    "bio_links": [{ "url": "https://meta.com" }],
    "emails_in_bio": [],
    "urls_in_bio": ["https://meta.com"]
}

Proxy

For best results, use Residential proxies with US location. Threads.net may block or rate-limit requests from datacenter IPs. The default configuration uses Apify Residential proxies (US) — no additional setup needed.

FAQ

What data can I extract from Threads.net? Posts (text, likes, replies, reposts, media), user profiles (bio, followers, verification), and full reply threads. The scraper also extracts emails and URLs found in text and bios.

How many posts or profiles can I scrape per run? There is no hard limit. The Actor processes up to 20 requests concurrently, with 5 retry attempts per request. A typical run can process hundreds of search results or profiles.

Does the Threads scraper handle private accounts? No. Only publicly visible data from public profiles and posts is collected.

What proxy should I use for Threads scraping? Residential US proxies are recommended. The default configuration already uses Apify Residential (US) — it works out of the box.

Can I search for accounts instead of posts? Yes. Set serp_type to accounts to search for Threads user profiles matching your keywords instead of posts.

What's the difference between the monthly and pay-per-use plans? Identical functionality. Monthly ($20/mo) is better for regular monitoring; pay-per-use ($2/1k results) is better for one-time scraping.

Support

Questions, bug reports, or feature requests: afrcanec@gmail.com