Threads Scraper

Public Threads profiles and posts as clean JSON — followers, bios, latest threads, replies, likes, images and videos.

Scrapes public Threads profiles and posts: follower counts, bios, and the latest threads with text, likes, replies, images and videos, from a profile or post URL. Give it a profile URL and it returns the account plus its most recent threads; give it a post URL and it returns the post plus the replies under it. Built for social-listening teams, creator-economy analysts, brand monitors and researchers who need Threads data without a Meta login.

⚡ Quick start

{ "startUrls": [{ "url": "https://www.threads.net/@zuck" }], "maxItems": 5 }

🧩 Input

Field	Type	Required	Default	Description
startUrls	array	yes	—	Threads profile or post URLs to scrape, e.g. https://www.threads.net/@zuck (profile plus latest threads) or https://www.threads.net/@zuck/post/C8CTu0iswgv (post plus replies). Both threads.net and threads.com links are accepted.
usernames	array	no	—	Threads handles to scrape as profiles, with or without the leading @, e.g. zuck or @meta. Each one is treated like a profile start URL.
maxItems	integer	no	5	Maximum number of dataset items per start URL. For a profile this is the profile item plus its latest threads; for a post it is the post plus its replies.
proxyConfiguration	object	no	{ "useApifyProxy": true }	Apify proxy settings used for the run. Datacenter proxies are enough for public Threads pages; switch to residential if runs start hitting the login wall.

Supported start URLs:

• https://www.threads.net/@<username> — the profile and its latest threads
• https://www.threads.net/@<username>/post/<code> — one post and its replies
• https://www.threads.net/t/<code> — one post and its replies (short link)

📤 Output

Every row carries an itemType of either profile or thread. A profile start URL yields one profile row followed by thread rows; a post start URL yields the post as a thread row followed by its replies, which are marked with isReply: true and point back via parentCode. Fields that only apply to one type are absent on the other.

Fields

Field	Type	Description
itemType	string	profile or thread.
url	string	Public URL of the profile or post.
username	string	Handle of the account (profile) or the post author (thread).
is_private	boolean	Profile only. Whether the account is private.
is_verified	boolean	Profile only. Whether the account carries a verified badge.
profile_pic	string	Profile only. URL of the profile picture.
full_name	string	Profile only. Display name.
bio	string	Profile only. Biography text.
bio_links	array	Profile only. External links in the bio.
followers	integer	Profile only. Follower count.
text	string	Thread only. Post text.
published_on	integer	Thread only. Unix timestamp (seconds) when the post was published.
id	string	Thread only. Full post id (<pk>_<user_pk>).
pk	string	Thread only. Numeric post id.
code	string	Thread only. Short code used in the post URL.
user_pic	string	Thread only. Author profile picture URL.
user_verified	boolean	Thread only. Whether the author is verified.
user_pk	string	Thread only. Author numeric id.
user_id	string	Thread only. Author id.
has_audio	boolean	Thread only. Whether an attached video has audio.
reply_count	integer	Thread only. Number of direct replies.
like_count	integer	Thread only. Number of likes.
images	array	Thread only. Image URLs attached to the post.
image_count	integer	Thread only. Number of attached images.
videos	array	Thread only. Video URLs attached to the post.
isReply	boolean	Thread only. true when the row is a reply collected from a post URL.
parentCode	string	Thread only. Short code of the post a reply belongs to.
repostCount	integer	Thread only. Number of reposts.
quoteCount	integer	Thread only. Number of quote posts.

💡 Use cases

• Track follower growth and engagement of brands, creators and competitors on Threads.
• Collect replies under a post for sentiment analysis and community research.
• Archive an account's latest threads, images and videos for reporting.
• Feed Threads posts into social-listening dashboards alongside other networks.

❓ FAQ

• Do I need a proxy? The Actor defaults to Apify datacenter proxies, which are enough for public profiles and posts. If runs start hitting a login wall, switch proxyConfiguration to a residential group.
• Do I need a Threads account? No. Only public profiles and posts are scraped, without logging in.
• How many results can I get? maxItems caps rows per start URL (the profile row counts as one). Threads shows only the most recent handful of posts on a profile without logging in, so a profile typically yields up to about ten threads; post pages return the post plus its visible replies. Add more start URLs or usernames to widen coverage.
• Can I use threads.com links? Yes. Threads moved to threads.com; both threads.net and threads.com URLs are accepted.
• Why did a run return fewer items than expected? Private accounts, deleted posts and very short feeds yield fewer rows. If a public page returns nothing, the site may have changed its layout — open an issue and we will update the Actor.

🔗 More scrapers by Anyx

• X (Twitter) Scraper
• Bluesky Scraper
• Reddit Scraper
• TikTok Trending Hashtags Scraper

🤝 Anyx Solutions

We build custom scrapers and data-extraction pipelines.

• Email: tantosthor@gmail.com

🖼 Image credit

Image credit: threads.net