Threads Scraper

Extract public data from Threads by Meta — profiles, posts, follower counts, engagement metrics, and keyword search results — without needing a Threads account or API key.

Built on the Apify platform using Crawlee + TypeScript.

When to use this (AI agents): call this tool when you need public Threads data for a given username or keyword — a profile's bio/follower count, a user's recent posts with engagement metrics, or accounts matching a search term. No login or API key required. Not for private/DM data.

---

What it does

• Profile scraping — given one or more Threads usernames, returns the profile record (bio, follower count, verified status) plus their most recent posts.
• Post data — per post: text, like count, reply count, repost count, quote count, publish timestamp, and any attached image/video URLs.
• Keyword search — searches Threads for a term and returns matching public profiles (Threads' logged-out search is account search, so results are accounts, not posts).
• Bulk runs — supports lists of usernames and multiple search terms in a single Actor run.

---

Input

Field	Type	Default	Description
profiles	string[]	["zuck"]	Threads usernames or profile URLs to scrape
searchTerms	string[]	[]	Keywords or phrases to search
postsPerProfile	integer	25	Max posts returned per profile (1–200)
resultsPerSearch	integer	25	Max profiles returned per search term (1–200)
proxyConfiguration	object	Apify Residential	Proxy settings — residential strongly recommended

Minimal input example

{
    "profiles": ["zuck", "mosseri"],
    "postsPerProfile": 50
}

Search example

{
    "searchTerms": ["AI tools", "web scraping"],
    "resultsPerSearch": 100
}

---

Output

Each Actor run pushes records to the default dataset. Two record types are produced:

Profile record (type: "profile")

{
    "type": "profile",
    "userId": "314216",
    "username": "zuck",
    "fullName": "Mark Zuckerberg",
    "biography": "Founder & CEO of Meta",
    "profilePicUrl": "https://...",
    "isVerified": true,
    "followerCount": 12000000,
    "url": "https://www.threads.net/@zuck",
    "scrapedAt": "2024-06-23T10:00:00.000Z"
}

Post record (type: "post")

{
    "type": "post",
    "postId": "3398765432100001234",
    "code": "C8xABCDEFgh",
    "url": "https://www.threads.net/@zuck/post/C8xABCDEFgh",
    "authorUsername": "zuck",
    "authorId": "314216",
    "text": "Threads just hit 300M monthly actives.",
    "likeCount": 45000,
    "replyCount": 1200,
    "repostCount": 300,
    "quoteCount": 80,
    "publishedAt": "2024-06-01T12:00:00.000Z",
    "imageUrls": [],
    "videoUrls": [],
    "scrapedAt": "2024-06-23T10:00:00.000Z"
}

Note on search results: keyword search returns profile records (type: "profile") — Threads' logged-out search matches accounts, not posts. Post records (with engagement metrics) come from profile scraping via profiles, not from searchTerms.

---

Pricing

This Actor uses Pay-Per-Event (PPE) pricing:

Event	Charged when
profile-scraped	A profile record is successfully scraped and saved
post-scraped	A post record is successfully scraped and saved

Failed items and error records are not charged. You only pay for data you actually receive.

---

Proxy

Threads aggressively rate-limits and blocks datacenter IPs. Residential proxies are strongly recommended and are the default. The Actor will not function reliably without proxy rotation.

---

Legal & compliance notice

This Actor scrapes publicly available data only — profiles and posts that any visitor can read on threads.net without logging in. It does not access private accounts, direct messages, or any authenticated content.

The user (buyer) bears sole responsibility for how they use the data collected, including compliance with:

• Meta's Terms of Service and Threads Community Guidelines
• Applicable data protection laws (GDPR, CCPA, and others)
• The laws of the jurisdiction in which they operate

This tool is intended for legitimate use cases such as public research, brand monitoring, academic analysis, and journalistic investigation of public figures and public interest content. Misuse is the responsibility of the operator.

---

FAQ

How do I scrape Threads without an account or API key? Pass Threads usernames (or profile URLs) into profiles and run — no login required. The Actor reads the same public data any visitor sees on threads.net.

Can I get follower counts and post engagement metrics? Yes. Each profile record includes follower count and verified status; each post record includes like, reply, repost, and quote counts, timestamps, and image/video URLs.

How do I search Threads by keyword? Add terms to searchTerms. Threads' logged-out search is account search, so the Actor returns matching public profiles (type: "profile"), not posts. To get posts with engagement metrics, pass those accounts' usernames to profiles.

Do I need residential proxies? Yes — strongly recommended and set by default. Threads aggressively rate-limits and blocks datacenter IPs, so the Actor won't run reliably without residential proxy rotation.

What does it cost? Pay per event — you're billed per profile and per post successfully saved. Failed items and error records are not charged.

Is scraping Threads legal? This Actor accesses only public profiles and posts — no private accounts or DMs. Content is still personal data under GDPR/CCPA — you are responsible for lawful use and for complying with Meta's Terms. See the notice above.

---

Related Actors by Ratio Tech

Monitoring social platforms? See also:

• Bluesky Scraper — public profiles, posts, and keyword search via the AT Protocol