Threads Profile Scraper avatar

Threads Profile Scraper

Pricing

from $13.50 / 1,000 items

Go to Apify Store
Threads Profile Scraper

Threads Profile Scraper

Scrapes Threads posts from public profiles by username. Returns each post as a flat row with text, timestamp, and engagement metrics.

Pricing

from $13.50 / 1,000 items

Rating

0.0

(0)

Developer

ParseForge

ParseForge

Maintained by Community

Actor stats

0

Bookmarked

13

Total users

0

Monthly active users

6 days ago

Last modified

Share

ParseForge

Threads Profile Scraper

Scrape Threads posts from any public profile, up to a million per run. Get each post's text, timestamp, and engagement metrics in a flat row. No login or API key. Export to CSV, JSON, Excel, or XML.

Threads has no official public API for profile data, and the unofficial endpoints are unstable and rate-limited. This Actor reads public Threads profiles directly, using a stealth browser and residential proxies, and returns each post in one fixed schema. Feed it a list of usernames and get the latest posts from each.

Who uses itWhat they scrape Threads for
Social media managersMonitor competitor accounts and track their posting frequency and engagement.
Market researchersAnalyze what topics and formats are resonating with audiences on Threads.
JournalistsArchive public statements and announcements from public figures and brands.
Data analystsBuild datasets of Threads posts for trend analysis and reporting.

What it does

This Actor collects Threads posts from public profiles by username and returns each post as a flat row.

  • ๐Ÿ‘ค Profile scraping: provide a list of Threads usernames and get their latest posts.
  • ๐Ÿ“Š Structured output: each post is returned as a flat row with text, timestamp, and engagement metrics.
  • ๐Ÿ” Bulk collection: scrape up to 1,000,000 posts per run across multiple profiles.
  • ๐Ÿ›ก๏ธ Stealth and proxies: uses Camoufox and residential proxies to avoid blocks and rate limits.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Threads data

๐Ÿ“ˆ Track competitor activity.

A social media manager runs the Actor daily on a list of competitor usernames to see what they post and how often, then adjusts their own content calendar.

๐Ÿ” Research audience interests.

A market researcher scrapes posts from industry leaders and analyzes the text to identify trending topics and engagement patterns.

๐Ÿ—ž๏ธ Archive public statements.

A journalist collects posts from public figures and brands to preserve statements for fact-checking and reporting.

๐Ÿ“Š Build a dataset for analysis.

A data analyst scrapes thousands of posts from selected profiles and exports them to CSV for sentiment analysis or trend modeling.

Why choose this scraper

What you get
No API keyScrape public Threads profiles without registering an app or dealing with OAuth.
Stealth browserCamoufox and residential proxies reduce the chance of blocks and CAPTCHAs.
Flat schemaEvery post comes back in the same structure, ready for analysis or export.
ScalableCollect up to a million posts per run, across any number of profiles.

How it compares

This Actor focuses on scraping Threads profile posts, while the competitors below offer broader contact extraction or ad library data that includes Threads.

FeatureParseForgeContact Details ScraperFacebook Ads Library Scraper
Scrape Threads profile postsYesNot listedNot listed
Extract post text and timestampYesNot listedNot listed
Collect engagement metricsYesNot listedNot listed
Bulk scrape multiple profilesYesNot listedNot listed
Export to CSV, JSON, Excel, XMLYesNot listedNot listed

Configure the run

Drive the Actor with a list of Threads usernames, and set the maximum number of posts to collect per run. The Input tab lists every parameter.

A first run with the defaults:

{
"maxItems": 10,
"usernames": [
"zuck",
"mosseri",
"openai",
"mkbhd",
"apify",
"instagram",
"threads",
"nytimes",
"cnn",
"theverge",
"techcrunch",
"wired",
"garyvee",
"sahilbloom"
]
}

A larger pull:

{
"maxItems": 200,
"usernames": [
"zuck",
"mosseri",
"openai",
"mkbhd",
"apify",
"instagram",
"threads",
"nytimes",
"cnn",
"theverge",
"techcrunch",
"wired",
"garyvee",
"sahilbloom"
]
}

Pricing

Pay-per-result: $0.018 per result collected. You pay only for the results written to your dataset.

Results collectedApproximate cost
100 results$1.80
1,000 results$18.00
10,000 results$180.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

  1. Create a free Apify account with $5 in credit.
  2. Open the Threads Profile Scraper.
  3. Set your inputs and any filters, then click Start.
  4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to Threads through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/threads-search-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check that the usernames are spelled correctly and that the profiles are public. Also ensure that the maximum posts value is set to at least 1.

Why did the run stop early?

The Actor stops when it reaches the maximum posts limit or when there are no more posts to collect. If you need more posts, increase the limit.

Why am I getting blocked or seeing CAPTCHAs?

The Actor uses stealth techniques, but occasional blocks can happen. Try running again later or reduce the number of profiles per run.

Why are some posts missing?

Threads may not show all posts on the public profile page. The Actor collects what is visible without authentication.

Can I scrape posts from a specific date range?

The Actor collects the latest posts up to the maximum limit. It does not support date filtering.

FAQ

QuestionAnswer
Do I need a Threads account or API key?No. The Actor scrapes public profiles directly. You only need to provide the usernames.
Can I scrape private Threads accounts?No. The Actor only accesses public profiles. Private accounts are not accessible without authentication.
How many posts can I collect?You can set the maximum number of posts per run, up to 1,000,000. The Actor will stop when it reaches that limit or when there are no more posts.
What data do I get for each post?Each post is returned as a flat row with fields like text, timestamp, and engagement metrics. The exact fields are shown in the sample output.
Can I scrape multiple profiles in one run?Yes. Provide a list of usernames in the input, and the Actor will scrape each one sequentially.
How do I avoid getting blocked?The Actor uses Camoufox and residential proxies to mimic real user behavior and reduce the risk of blocks.
What formats can I export the data to?You can export the results to CSV, JSON, Excel, or XML directly from the Apify platform.
Can I schedule this Actor to run regularly?Yes. You can set up a schedule in Apify to run the Actor at intervals, such as daily or weekly.
Is this Actor legal to use?You should only scrape public data and comply with Threads' terms of service and applicable laws. The Actor does not bypass any authentication.
What if a username doesn't exist?The Actor will skip that username and continue with the others. You can check the run log for details.

Browse the full ParseForge collection for more scrapers.

๐Ÿ†˜ Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

โš ๏ธ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.