Threads Posts Scraper: User Posts & Post URLs

Scrape the posts of any public Threads account, or single posts by URL, with no login: text, likes, replies, reposts, shares, media and dates as a table.

User	Post	Likes	Replies	Views	Posted
zuck	We believe superintelligence will create significa…	2,754	2,668	436,171	2026-09-28
mosseri	Big day for the Muse team with the introduction of…	1,115	1,054	617,444	2026-10-12
mosseri	Every major platform has had to lean into recommen…	272	364	42,126	2026-10-22

What you can get

You type	You get
A username (mosseri, @mosseri, a profile URL)	The account's own posts, newest first, paged to the end of the account (up to 📊 Max posts per account)
... with Replies to others picked	The account's replies to other people, each with the post it answers (parentPostText, parentPostUsername)
... with Reposts picked	What the account reposted (Threads' reposts tab answered the latest 25 when tested, 2026-10-03): the original post plus who reposted it
... with Profile picked	One more row for the account: followers, bio, links, Instagram counts and its 10 latest posts (a result like any other)
A post URL (threads.com/@user/post/... or threads.com/t/...)	That post, with its viewCount

Use it to monitor competitors' or creators' posts on a schedule, archive an account, measure engagement per post, or collect posts for research and AI training.

Output

The Output tab opens on 🧵 Posts (author, text, likes, replies, reposts, quotes, shares, media, date) with 🖼️ Media and 👁️ Views and authors next to it. Every field has a label and a description in the dataset schema. Each row:

• who: username, fullName, profilePicUrl, isVerified
• what: text, textSnippet, url, createdAt, language
• engagement: likeCount, replyCount, repostCount, quoteCount, shareCount and viewCount (Threads hides many zero counts; those come back empty), viewCountStatus (why a view count is empty)
• media: mediaType, thumbnailUrl, mediaUrl, images, videos, mediaUrls and mediaUrlTypes (every image and video in order, with its type), hasMedia, mediaCount, carouselCount, musicTitle, musicArtist, musicAssetId, inline stickers (isStickerPost, stickerUrls)
• hashtags, mentions, links (real URLs, not Threads' redirect links), emails, topicTag, link preview (linkPreviewUrl, linkPreviewTitle)
• the account's own threads: threadPosition (1 = the first post of a thread the author chained) and threadFirstPostCode
• replies and quotes: isReply, replyToUsername, parentPostUrl, parentPostCode, parentPostText, parentPostUserId, parentPostRepostCount, parentPostQuoteCount, parentPostShareCount, parentPostAvailable, replyDepth, isQuotePost, quotedPostUrl, quotedPostText
• author (on by default, one lookup per author per run): authorFollowerCount, authorBio, authorProfilePicHdUrl, authorProfileTags, authorInstagramFollowerCount, authorBioLinks, authorEmails, authorPhones, authorFediverseEnabled, authorProfileUrl
• also: imageCount, gifUrl, gifDescription, canReply, areCountsHidden, transparencyLabel, isAiGenerated (empty when the post carries no AI-detection data)
• ids and source: postId, code, userId, inputType, input, scrapedAt
• reposts: isRepost, repostedByUsername, repostedAt, repostCode, isPinned

👁️ View counts on every post and 👤 Author details on every post are on by default: the Actor reads each post's page and each author's profile in parallel while rows stream (same price; turn them off for faster big runs). Threads doesn't show a view count on every post; viewCountStatus says why one is empty. Times are UTC. Picture and media links are signed by Threads and expire after a few days.

Need the comments under a post? Threads Replies Scraper gets its public replies on the same engine.

Speed

Plain HTTPS on Apify datacenter IPs, no browser, 256 MB. The prefilled run (10 post URLs, view counts and author details on) took 5-7 s on Apify in 4 runs on 2026-10-26, first result 0.9-1.4 s after the container started, peak memory 69-73 MB. On the Apify platform the same engine read 1,000 posts of @cnn in 64 s and 2,000 in 128 s (2026-10-03).

Posted after / Posted before keep only posts in a date window (a date like 2026-09-01 or a period like 7 days); posts outside it are not charged.

Pricing

Pay per result: $1.59 per 1,000 on Free, $1.29 on Starter, $1.09 on Scale and $0.89 on Business. No start fee. Only results in your dataset are charged; filtered posts and repeats are free. Set a maximum cost per run in the run options and the run stops exactly there. A run that Apify restarts never charges a result twice.

FAQ

Do I need a Threads or Instagram account? No. Everything comes from what Threads shows logged-out visitors, through Apify datacenter IPs (residential only as a fallback, at no extra cost to you).

How far back does it go? To the account's first post, if you set 📊 Max posts per account high enough.

Private accounts? Their posts aren't public, so you get none and pay nothing; the run summary (OUTPUT) says the account is private.

Is there a Threads API for posts? Meta's official Threads API only reads your own account. Call this Actor from the Apify API, a schedule or an integration and get JSON, CSV or Excel for any public account.

Related Actors

• Threads Scraper: search, profiles, posts and replies in one Actor.
• Threads Search Scraper: posts or accounts by keyword or hashtag.
• Threads Profile Scraper: followers, bio, links and the linked Instagram's counts.
• Threads Replies Scraper: the public replies under a post, 3 levels deep.

Feedback

Missing a field or an input type? Open an issue on the Actor's page; we answer quickly. If the data helped you, a short review on the Store page helps others find it, and helps us a lot.