Threads Profile & Posts Scraper

Scrape Threads profile info + posts

Description

Scrape Threads profile info + posts. Extract follower count, bio, profile details, AND 15-50 posts per profile. More data than profile-only scrapers at 40% lower cost. JSON, CSV, Excel export.

Features

📌 Status 🧠 Context [2026-03-12] — outputSchema description added (spec-005)

How It Works

This actor uses intelligent extraction with Apify's proxy infrastructure to gather public data from Threads Profile & Posts Scraper. It handles authentication, pagination, and error recovery automatically.

Quick Start

# Run via Apify API
apify run -a red.cars/threads-scraper

# Or configure input and click Run on:
# https://apify.com/red.cars/threads-scraper

Using as an MCP Tool

Running on Apify Platform

Set APIFY_API_KEY in your Apify Console secrets, configure input via the Actor input schema UI, and click Run.

Input Schema

Parameter	Type	Description	Default
urls	array	Enter Threads usernames or profile URLs. Examples: 'nike', '@cnn', 'https://www.threads.net/@zuck'	nike,cnn
maxPosts	integer	Maximum posts to extract per profile	5
includeComments	boolean	Extract comments for each post	false
maxResults	integer	The maximum total number of items to extract.	5
proxyType	string	Choose your preferred balance of cost vs reliability. Standard (Datacenter) is faster; Premium (Residential) is most reliable for high-security targets. Options: DATACENTER, RESIDENTIAL	RESIDENTIAL
debugMode	boolean	Enable minimal extraction for health checks and testing. Guarantees success within 300s.	false
exportFormat	string	Choose output format. Use 'markdown' for token-efficient LLM-ready Threads content. Options: json, csv, markdown	json
checkOnly	boolean	When true, returns immediately with capability metadata without scraping. Used by AI agents to verify availability before committing to a paid run. Free, <5 seconds.	false

Output Schema

Field	Type	Description
results	string	Meta Threads posts and user profiles with engagement data. Each result contains: type, username, displayName, bio, followers, isVerified (profiles) or postId, postText, timestamp, likes, replies, reposts, hashtags, mentions, mediaUrls (posts). Use for brand monitoring, influencer research, social listening on Threads. AI agents: search by @handle or keyword.

Example Output

{
  "results": [
    {
      "url": "https://example.com/profile",
      "username": "example_user",
      "fullName": "Example User",
      "followersCount": 10000,
      "followingCount": 500,
      "postsCount": 250,
      "isVerified": false,
      "biography": "Example bio text",
      "latestPosts": [],
      "scrapedAt": "2026-03-23T13:24:33.638Z"
    }
  ]
}

Pricing

Pay-per-event billing: you are charged only for what a run actually returns.

Event	Price
Actor start	$0.005 per run (one-time)
Scrape Profile	$0.005 per profile ($5 per 1,000)
Scrape Post	$0.005 per post ($5 per 1,000)

Platform usage (compute and proxy) is billed against your own Apify plan's usage, not added on top of the event prices above. A run that returns nothing charges nothing per result.

For a typical 100-profile pull with recent posts, expect roughly $1.05 in event charges plus your plan's compute and proxy usage.

Use Cases

• Influencer Research: Identify and evaluate potential influencers by engagement metrics and audience quality
• Competitor Monitoring: Track competitor presence and activity on Threads
• Lead Generation: Build targeted lead lists from public profiles and contact information
• Market Intelligence: Gather market intelligence and trend data for business decisions
• Content Aggregation: Collect content for analysis, archiving, or republication

FAQ

What exactly do I get per profile?

Profile details (username, display name, bio, follower/following/post counts, verified status) plus 15-50 recent posts per profile, each with post text, timestamp, likes, replies, reposts, hashtags, mentions, and media URLs. Set includeComments to true to also pull each post's replies.

Do I need an API key?

No. No API key or Threads account is required. The actor runs on Apify's proxy infrastructure.

How does pricing work?

Pay-per-event: $0.005 per actor start (one-time per run), $0.005 per profile scraped ($5 per 1,000), and $0.005 per post ($5 per 1,000). A run that returns nothing charges nothing per result. Compute and proxy usage bills against your own Apify plan, not on top of the event prices.

How is this different from other Threads scrapers?

Profile-only scrapers stop at the bio and follower counts. This actor returns profile details AND the latest posts with engagement data, at about 40% lower cost, with JSON, CSV, or LLM-ready Markdown export.

What inputs does it accept?

Plain usernames (nike), @handles (@cnn), or full profile URLs (https://www.threads.net/@zuck), mixed freely in the urls array. maxPosts caps posts per profile (default 5) and maxResults caps total items returned.

How many posts can I get per profile?

15-50 recent posts depending on the profile's activity and platform availability. Raise maxPosts (and maxResults) to collect more. Historical posts beyond the recent window are not available on Threads.

Which output format should I use?

json for pipelines and scripts, csv for spreadsheets, and markdown when feeding LLMs or RAG: it stays fully readable at a fraction of the tokens.

Which proxy should I choose?

DATACENTER is faster and cheaper; RESIDENTIAL (the default) is the most reliable against Threads' bot defenses. If a run returns fewer profiles than requested, switch to RESIDENTIAL and lower concurrency.

How do I increase success rate?

• Keep Premium (Residential) proxy for high-security targets
• Reduce concurrency for rate-limited profiles
• Use debugMode to smoke-test inputs before a full extraction

Can I run this on a schedule?

Yes. Use Apify Scheduler for cron-style recurring pulls of the same profiles. For AI agents, run with checkOnly: true first to verify capability before committing to a paid run.

Troubleshooting

Error	Cause	Fix
NETWORK_ERROR	Network connectivity issue	Check internet connection, retry with proxy
VALIDATION_ERROR	Invalid input parameters	Review input schema and retry
PLATFORM_ERROR	Threads platform issue	Threads may be throttling or having issues, try again later

Known Limitations

• Private accounts: Cannot extract data from private accounts without following
• Rate limiting: Platform may temporarily block repeated requests from same IP
• Data freshness: Extracted data reflects moment of extraction; historical data may be limited
• Proxy requirements: High-security targets may require residential proxy for reliable extraction
• Content limits: Platform-imposed limits on historical post retrieval

Legal

Data Source: Threads (threads.net)

Terms of Service: This actor is provided for legitimate data collection purposes only. Users must comply with Threads' Terms of Service and applicable laws. Red.cars is not responsible for misuse of this tool.

Privacy: All extracted data is processed in accordance with applicable privacy laws. Do not use this tool for unauthorized data collection or privacy-violating activities.

Attribution: When using Threads data, comply with their attribution requirements and data policies.

---

red.cars Intelligence Fleet • apify.com/red.cars