Threads Scraper

Extract public data from Threads (threads.net / threads.com), Meta's text social network — no login, no cookies, no proxy. Pull a user's posts, their replies / reposts / media tabs, keyword post search, user search, and a single post's thread, all as clean structured rows ready for analysis.

Who it's for

• Analysts & researchers — track a person or brand's posts and engagement, monitor keywords and topics over time.
• Agencies & lead-gen — find and qualify profiles by keyword: usernames, bio links, follower counts, verified status.
• AI / dataset builders — bulk public post text + engagement metrics for trend analysis and model training.

---

What you get (output fields)

Every row is tagged rowType = post or user.

post rows

Field	Description
pk / code	Numeric post id / shortcode
url	Canonical post URL
takenAt	Post time (epoch seconds)
caption	Full post text
username / userId / userFullName	Author handle, id, display name
userIsVerified / userProfilePicUrl	Author verified flag, avatar
replyCount / repostCount / quoteCount / reshareCount / likeCount	Engagement metrics
isReply / replyControl	Reply flag, who can reply
imageUrl / videoUrl / hasAudio	Media URLs / audio flag
sourceQuery	Which input produced the row

user rows

Field	Description
pk / username / fullName	Id, handle, display name
biography	Profile bio
followerCount	Follower count (profile-info mode)
isVerified / isPrivate	Status flags
profilePicUrl / bioLinks	Avatar, external links
url	Profile URL

---

Modes & use cases

Mode	Input	Returns	Use case
Profile posts	usernames, tab	posts	Track a creator's output; competitor monitoring
Profile info	usernames	1 user row/user	Enrich a list of handles with bio/followers/links
Search posts	searchQueries, recent	posts	Keyword & topic monitoring, trend capture
Search users	searchQueries	users	Discover creators/leads by keyword
Post detail	postUrls, includeReplies	post + replies	Pull a specific thread and its replies

• Profile posts support all four tabs — threads, replies, reposts, media — with deep pagination (set resultsPerProfile: 0 for everything available).
• Lead generation: run Search users on your niche keywords, then Profile info on the handles to get follower counts and bio links.
• Brand monitoring: run Search posts with recent: true on a schedule to capture every new mention chronologically.

---

Input

{
  "mode": "profile_posts",
  "usernames": ["zuck", "https://www.threads.com/@mosseri"],
  "tab": "threads",
  "resultsPerProfile": 0,
  "maxItems": 500
}

Field	Type	Default	Notes
mode	string	profile_posts	profile_posts, profile_info, search_posts, search_users, post_detail
usernames	array	[]	@handles, usernames, or profile URLs
tab	string	threads	threads, replies, reposts, media
searchQueries	array	[]	keywords/phrases
recent	boolean	false	search posts chronologically
postUrls	array	[]	post URLs or shortcodes
includeReplies	boolean	true	include a post's first page of replies
resultsPerProfile	integer	0	per-profile cap (0 = all)
maxItems	integer	200	global row cap

Example output (post)

{
  "rowType": "post",
  "pk": "3977518562965884838",
  "code": "Dcy_A8pGo-m",
  "url": "https://www.threads.com/@zuck/post/Dcy_A8pGo-m",
  "takenAt": 1788377183,
  "caption": "Muse Spark 1.3 is rolling out today ...",
  "username": "zuck",
  "userFullName": "Mark Zuckerberg",
  "userIsVerified": true,
  "replyCount": 208,
  "repostCount": 151,
  "quoteCount": 28,
  "likeCount": 1478,
  "imageUrl": "https://scontent.cdninstagram.com/...",
  "sourceQuery": "profile:zuck"
}

---

Scheduling & webhooks

Run it on a schedule (e.g. hourly keyword monitoring) from the Apify Console, and attach a webhook to push new rows straight into your database, Google Sheet, or Slack when a run finishes. Results export to JSON, CSV, Excel, or via the API.

Use with AI assistants (MCP)

This actor works as a tool for AI assistants through Apify's MCP server — an LLM agent can call it to pull live Threads data (e.g. "get the latest posts from @zuck" or "find Threads users posting about AI") as part of a larger workflow.

---

FAQ

Do I need a Threads or Instagram account? No. The actor reads only public data and requires no login, cookies, or tokens.

How fresh is the data? Live — every run hits Threads directly, so you get the current state at run time.

How deep can profile pagination go? Profile feeds paginate without an imposed limit — set resultsPerProfile: 0 to fetch everything available for a user.

Are there limits on search? Threads caps anonymous keyword post search at roughly 20 results per query, and results vary between calls, so schedule repeated runs to capture more. User search returns up to ~85 per query. Profile feeds are not capped.

Can I get replies to a post? Yes, via Post detail — note that anonymous access reaches the first page of replies for a given post.

Is scraping Threads legal? This actor collects only publicly available data. You are responsible for using the output in line with Threads' terms and applicable laws (e.g. GDPR/CCPA) in your jurisdiction.

Something broke or a field is missing? Threads changes its site periodically. Open an issue on the actor and it will be fixed.