Threads Scraper — Posts, Profiles, Search & Hashtags
Pricing
Pay per usage
Scrape Threads posts, profiles, hashtags and search results without login. Exact like/reply/repost counts, images, videos, batch mode, pay per result.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Parker
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
10 days ago
Last modified
Categories
Share
All notable changes to this Actor are documented here.
The format is based on Keep a Changelog , and this project adheres to Semantic Versioning .
The reliability release. Extraction no longer depends on the Threads UI, maxItems
is delivered in full, and batch mode actually works.
scrapeMethod (embedded | graphql | dom) so degradation is visible in the
dataset instead of silent.likes, replies and reposts come from the payload
as integers. The DOM parser reported Threads' abbreviated labels, so 1.5K became
1500 and a profile with 5,687,751 followers was recorded as 5,600,000.stats.quotes — quote-post counts, previously unavailable.actor-start, post-output,
profile-output. Items are charged only after they are stored, and maxItems is
capped up front to what the run's budget covers. Reaching the charge limit ends the
run as a success with a status message, never a failure.keywords, usernames, tags,
postUrls and concurrency were implemented but invisible on the Console.maxReplies for the post action, and flat requestDelayMs / maxRetries fields.
The rateLimitConfig object form still works and is overridden per key.RUN_SUMMARY key-value record per run: items per source, the extraction engine
mix, charged events, and why the run stopped. Linked from the Output tab.type, source, parentId,
profile, scrapeMethod, stats.shares and stats.quotes as described fields.images.en-US, and automatic session rotation on a login wall or rate
limit. When login cookies are supplied, fingerprint rotation is disabled and the
pool is pinned to one session — rotating devices under a single real identity is an
account-ban signal.maxItems under-delivery. Three separate counters disagreed, and posts that
failed validation still consumed the quota, so runs routinely returned fewer items
than requested. A single budget now counts only stored items.concurrency > 1. On the shared queue a
crawler could pick up another crawler's request and run the wrong handler on it,
producing profile records scraped from a search page. Each crawler now owns a
private queue.blocked, unavailable and Try again anywhere in the page, which
ordinary Threads chrome contains.rateLimitConfig and includePosts, and skipped input validation.followingCount and postsCount in missingFields
rather than leaving them silently absent. Threads does not expose either field to
anonymous requests.post run had no source, leaving an empty column in the
Output tab.followingCount and postsCount are not available without login — Threads omits
them from anonymous responses entirely.Initial release.
storageState, unlocking the
location and joinedDate profile fields.