Threads Scraper - Posts, Profiles & Search

Collect public Threads posts, profile details, keyword results, and user discovery results through ScrapeCreators. No Threads login or cookies required. The owner configures SCRAPECREATORS_API_KEY privately; buyers never provide a provider key.

Inputs

• posts: handles with usernames or Threads profile URLs; recent public posts.
• profiles: handles; profile name, biography, followers, verification and bio links.
• post: postUrls; single posts, optionally includeReplies for visible public replies.
• search: queries; keyword discovery with optional startDate and endDate in YYYY-MM-DD.
• users: queries; discover public users by username. Discovery results have fewer profile fields; missing fields remain null.

{"mode":"posts","handles":["zuck"],"maxResults":5,"maxResultsPerTarget":5,"maxRequests":2}

{"mode":"search","queries":["technology"],"maxResults":10,"maxRequests":2}

{"mode":"profiles","handles":["zuck"],"maxResults":1,"maxRequests":2}

Results are deduplicated by stable profile/post identity. Each row has type, id, url, username, source and scrapedAt. Post rows include text, UTC publish time, nullable engagement counts, hashtags, mentions, and available image/video URLs. Profile rows include nullable biography, follower count, verification, picture URL and bio links. Diagnostics are in the OUTPUT key-value record.

Limits and reliability

The provider exposes recent public windows, not complete account history. Its documentation describes approximately 20–30 recent user posts and about 10 keyword results, but observed counts vary. No documented cursor pagination is advertised. Related posts and author continuation posts from the detail endpoint are excluded. Replies are limited to the visible window returned by that endpoint. Media URLs may expire. Private or unavailable content is not collected.

maxResults caps the whole dataset; maxResultsPerTarget caps each input target. Verified free-plan runs are capped at five delivered business records, before provider calls and before writes. An unknown local plan does not trigger this cap. At most 20 input targets and 20 provider attempts are allowed. Defaults: 20 total records, 20 per target, 10 provider attempts. The Actor runs sequentially, uses a 45-second request timeout, at most one retry, and a 170-second internal deadline. It stops after two consecutive provider failures and preserves partial results. Input is validated before API calls. API failures are explicit; no fabricated records or silent success.

Pay per event

All-in proposed tier prices (live verification required):

Event	FREE	BRONZE (2.5%)	SILVER (5%)	GOLD (20%)
Actor start	$0.020	$0.0195	$0.019	$0.016
Unique dataset result	$0.010	$0.00975	$0.0095	$0.008

FREE examples: one result $0.03, five results $0.07, twenty results $0.22. Start fee applies even when no public result is available. No result event is charged for empty, rejected, or failed targets. One synthetic dataset event per delivered record; no manual or duplicate charge. Platform-usage pass-through is disabled. Charge limits can reduce delivery; maxRequests separately bounds provider work. Provider invoices are distinct from Apify compute usage. Final prices depend on measured canaries and verified live settings.

Use public data for a legitimate purpose and comply with applicable law and platform/provider terms. This Actor is independent of Meta and Threads.

Development

Node.js 22 and Apify SDK 3. Run npm ci, npm test, then apify run with the owner's provider key in the environment. Cloud secrets use @SCRAPECREATORS_API_KEY. New Actor and Tasks remain private until owner publication.