Threads Scraper alternative: subimpact Threads Scraper
Both actors read public Threads accounts and post pages without a login and return posts with text, time, likes, replies, reposts and quotes. futurizerush/meta-threads-scraper lists $2.50 per 1,000 results on both plans plus a start fee. Ours lists $1.00 per 1,000 posts and $2.00 per 1,000 profiles, with no start fee. Theirs searches by keyword and hashtag and finds accounts by keyword; ours works from profile and post links and adds profile rows. Both run on the Apify Store.
Prices checked 20 Nov 2026. Both actors run on Apify, so the numbers come from the same Store listing pages.
Key facts side by side
| Fact | Threads Scraper - Posts, Profiles & Search | This API (Threads Scraper: Profiles, Posts & Replies) |
|---|---|---|
| Price per 1,000 posts (Free plan) | $2.50 | $1.00 |
| Higher plans (Gold) | $2.50 | $1.00 |
| Start fee per run | $0.02 | None |
| Platform usage | Included | Included |
| Users on the Apify Store | 9,448 | 5 |
| Rating | No reviews yet | No reviews yet |
| Last build | 19 Nov 2026 | 18 Nov 2026 |
| Pricing model | Pay per event | Pay per event |
Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price.
Head-to-head test
15 posts from the @nasa Threads profile
| Measure | Threads Scraper - Posts, Profiles & Search | This API |
|---|---|---|
| Status | SUCCEEDED | SUCCEEDED |
| Items returned | 8 | 16 |
| Run time (seconds) | 8.1 | 9.6 |
| Average filled fields per item | 46.4 | 19.4 |
| Distinct fields | 99 | 39 |
| List price of the job | $0.04 | $0.016 |
| Measured platform usage | $0.08 of compute, included in the price | $0.0002 of compute, included in the price |
One run each on 20 Nov 2026, same input, default memory. Small samples; your results will vary with input.
Which one to choose
When to choose Threads Scraper - Posts, Profiles & Search
- You need keyword or hashtag search across Threads rather than named accounts.
- You want a sort order and a language preference on search results.
- You want date bounds applied inside the run for older or newer posts.
- You want media type and a view count status on each row.
When to choose this API
- You want a lower per row price and no separate run start charge.
- You want profile rows with followers and bio in the same dataset as posts.
- You want replies from a post page delivered as ordinary post rows.
- You work from a known list of accounts rather than a keyword.
Switching from Threads Scraper - Posts, Profiles & Search
| Their input field | Our input field | Note |
|---|---|---|
mode | (none) | No mode switch; the actor decides from whether you pass usernames, postUrls or both. |
usernames | usernames | Same key; handles, @handles and full profile links are all accepted. |
post_links | postUrls | Same meaning under a different name; each link gives the post and, when enabled, its visible replies. |
max_posts | maxPostsPerProfile | Same cap, now set per profile, with maxItems as a run wide ceiling. |
keywords | (none) | No keyword search input; start from known accounts and read their post text instead. |
start_date | (none) | No start date filter; filter the delivered rows on createdAt. |
end_date | (none) | No end date filter; the same createdAt filter covers it after delivery. |
Example input
{
"usernames": [
"zuck",
"nasa"
],
"maxPostsPerProfile": 15,
"includeReplies": true,
"maxRepliesPerPost": 20,
"maxItems": 200,
"proxyConfiguration": {
"useApifyProxy": true
}
}Actor id: subimpact/threads-scraper. Paste the input above into the Apify Console and press Start.
Where each one is stronger
Where Threads Scraper - Posts, Profiles & Search is stronger
- Searches posts by keyword or hashtag and can find accounts by keyword
- Output adds media type and a status field for missing view counts
- Larger user base and more recent runs on the Apify Store
Where this API is stronger
- Post and profile rows share one dataset, told apart by a rowType field
- Profiles are charged only when delivered, and profiles that do not exist are free
- No separate run start charge on top of the per row price
Questions people ask
How do the prices compare per 1,000 posts?
futurizerush lists $2.50 per 1,000 dataset items on both plans, plus a $0.02 start fee per run. Ours lists $1.00 per 1,000 posts or replies and $2.00 per 1,000 profile rows, with platform usage included and no start fee. Only delivered rows are charged on our side.
Can I search Threads by keyword or hashtag?
No. There is no search, hashtag or home feed input, which is the clearest place where their actor does more. Ours works through profile and single post links, so keyword research needs a different route, such as starting from known accounts and reading their post text.
Does the output shape carry over?
No. Their rows use snake case names such as text_content, created_at, like_count and post_code, while ours use rowType, text, createdAt, likes, replies, reposts, quotes and postCode. A pipeline that reads their columns needs a mapping layer, but the underlying content, dates and counts describe the same public posts.
Do I need a Threads or Instagram login?
No. The actor reads public pages over plain HTTP, with no cookies, no account and no browser. That means public accounts only: a private profile or a login wall comes back as not_found_or_login_wall and is not charged, and only what a logged out visitor sees is returned.
How many posts per profile can I get?
threads.com serves one profile page of about 15 threads with no deeper pagination, so maxPostsPerProfile is capped at 50 but asking for more does not fetch older threads. Set it to 0 when you only want the profile row with its follower count and bio.
Are all replies to a post returned?
Only the replies threads.com renders on the post page, and only when you pass the link in postUrls with includeReplies on. There is no way to page through further replies, so maxRepliesPerPost caps what is visible rather than fetching more of the thread.
How do I switch over from their actor?
Move usernames across unchanged, rename post_links to postUrls, and rename max_posts to maxPostsPerProfile. Drop mode, keywords, sort order and the date fields, which have no input here, then check any code that reads snake case columns before the first scheduled run.
Need a data source that is not here?
We build and run scrapers for sites that have no public API. Tell us the site, the fields and how often you need them.