Threads User Posts Scraper

Scrape a Threads (Meta's text app) user's profile feed by username or user ID. Returns clean, structured data for each post: text, like / reply / repost / quote / reshare counts, image and video URLs, timestamp, the post permalink, and author info. Optionally also scrape the user's replies and reposts.

Unofficial. This Actor is not affiliated with, authorized, or endorsed by Threads, Instagram, or Meta Platforms, Inc. It is an independent tool that retrieves publicly available data via a third-party API. Use it in compliance with Threads' terms and all applicable laws; you are responsible for how you use the retrieved data.

What it does

• By username — give one or more Threads handles (e.g. zuck); the Actor resolves each to its numeric profile id, then paginates the profile feed.
• By user ID — give numeric profile IDs directly to skip username resolution.
• Posts / replies / reposts — choose which feed(s) to pull per user via contentType, or add replies/reposts on top with the toggles.

Input

Field	Type	Default	Description
usernames	string[]	["zuck"]	Threads handles to scrape (with or without @). Each is resolved and paginated independently.
userIds	string[]	[]	Numeric profile IDs to scrape directly.
contentType	enum	posts	posts / replies / reposts / all.
includeReplies	boolean	false	Also scrape replies (additive to contentType).
includeReposts	boolean	false	Also scrape reposts (additive to contentType).
maxItems	integer	25	Max total posts across all users and feeds.

Example input

{
  "usernames": ["zuck", "mosseri"],
  "contentType": "posts",
  "includeReplies": true,
  "maxItems": 100
}

Output

One dataset item per post:

{
  "id": "3906263078447871896_63055343223",
  "pk": "3906263078447871896",
  "code": "DY11ZLWG_eY",
  "url": "https://www.threads.net/@zuck/post/DY11ZLWG_eY",
  "text": "Today Biohub is sharing a major scientific advance...",
  "takenAt": 1779882868,
  "likeCount": 1948,
  "replyCount": 385,
  "repostCount": 124,
  "quoteCount": 0,
  "reshareCount": 66,
  "imageUrls": ["https://..."],
  "videoUrls": [],
  "coverUrl": "https://...",
  "author": {
    "pk": "63055343223",
    "username": "zuck",
    "fullName": null,
    "isVerified": true,
    "profilePicUrl": "https://..."
  },
  "source": "posts:zuck"
}

Notes

• Data is sourced live; Threads occasionally rate-limits, so the Actor retries transient blocks with exponential backoff.
• Post IDs are de-duplicated within a run.
• Pagination follows the feed's end_cursor until there are no more pages.

Quick start

1. Open the Actor and press Run — the default input works out of the box.
2. Adjust the input fields below to your target (keywords, IDs, or URLs) and set maxItems to cap spend.
3. Grab results from the Dataset tab as JSON / CSV / Excel, or pull them via the Apify API and MCP from your own code.

No proxies to configure, no cookies to paste, no login — the Actor handles everything server-side.

Why teams switch to this Threads user scraper

Tracking a Threads account through browser-based scrapers means babysitting failed runs — the most-used alternative completes fewer than half of its runs. This Actor reads a direct HTTP API: give it usernames, get their posts with full engagement metrics as clean JSON at $2.50 per 1,000 posts.

What people build with it

• Creator analytics — pull a creator's last 200 posts and chart what formats and topics drive their engagement.
• Competitor feeds — archive competitors' Threads output on a daily schedule; spot campaigns the moment they start.
• Influencer vetting — real per-post engagement (not the media-kit average) before you sign a partnership.
• Social listening — follow executives and journalists in your space; their posts are tomorrow's industry narrative.
• Repurposing pipelines — your own best-performing posts, exported as JSON, feed cross-posting and newsletter workflows.

Tips for better results

• Usernames work with or without @.
• Posts carry like / reply / repost / quote counts plus media URLs — filter for videoUrls / imageUrls to study a creator's format mix.
• Start from keywords instead with Threads Search, or find accounts via Threads Profile Search.

---

Why this Actor

• Direct API, no headless browser — fast, stable runs with nothing to babysit.
• No login, no cookies — we never touch your accounts, so there's no ban risk.
• Fresh, real-time data — every run reads the source live, not a stale cache.
• Pay per result — you're billed only for the rows actually delivered.
• Structured JSON — export to CSV, Excel, or JSON, or pull straight from the API / MCP.

Use cases

• Pull structured content + engagement for analytics dashboards.
• Track a creator's or topic's output and performance over time.
• Build training/research datasets of posts and metadata.
• Power competitor and trend monitoring.

FAQ

Do I need an account, cookies, or to log in anywhere? No. The Actor talks to a fast, direct HTTP API server-side — you just provide inputs and run it.

How am I billed? Pay-per-result: a fixed price per row returned, with no separate platform/compute charge. Caps like maxItems keep spend predictable.

Can I run it on a schedule or call it from my app? Yes — use Apify Schedules, the REST API, the JavaScript / Python clients, or the MCP server. See the API tab.

Is this affiliated with Threads? No. It's an independent tool that collects publicly available data. Use it in line with the platform's terms and applicable law.

More Threads scrapers by us

• Threads Search — Top & Recent posts by keyword
• Threads Profile Search — Find users by keyword
• Threads Post Replies — Replies by post ID or URL

Browse the full fleet → https://apify.com/ethereal_wool