Threads Scraper — Posts, Profiles, Replies | from $1.50/1K

Scrape Meta Threads posts by username or keyword — no login, no API key, just results.

What you get

Field	Description
post_id	Unique numeric post ID
code	Short code (appears in post URL)
post_url	Direct link to the post
author_username	Author's handle
author_id	Numeric author ID
author_verified	Verified badge
text	Full post text
taken_at	Posted timestamp (ISO-8601 UTC)
like_count	Number of likes
reply_count	Number of replies
repost_count	Number of reposts
quote_count	Number of quotes
is_reply	Whether this is a reply to another post
reply_to_username	Who this post replies to (if applicable)
media_urls	List of image/video URLs
media_types	Media type per URL (image/video/carousel_image)
has_media	Quick boolean — does this post have media?
link_preview_url	External URL if the post has a link preview

Modes

User mode (default)

Scrapes the latest posts from a specific Threads profile.

• Returns up to 25 most recent posts
• Input: username (e.g. zuck)

Keyword mode

Searches Threads for posts matching a keyword or phrase.

• Returns 10–30 results from Threads search
• Reply/repost counts included
• Input: keyword (e.g. AI tools, python tutorial)

Pricing

Pay-per-result: $1.50 per 1,000 posts. You only pay for posts actually returned.

Technical notes

• No authentication required — uses Threads' public web surface
• Rung 1 access — embedded GraphQL/relay JSON, no HTML parsing
• Residential proxy recommended for best reliability (included via Apify proxy)
• User mode: calls POST /api/graphql with the public session token extracted from the page
• Keyword mode: parses the embedded Relay preloader from the search results page

Limitations

• User mode returns up to ~25 most recent posts per profile (Threads API limit on public endpoint)
• Keyword mode returns what Threads surfaces on the search page (10–30 posts)
• Private profiles return 0 posts (as expected — no login)
• Reply/repost counts are populated in keyword mode; in user mode they are 0 unless the post detail page is fetched separately

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.