Threads Posts, Search, Profiles & Replies Scraper

Extracts available public Threads search results, post metadata, public profile summaries, and replies into structured dataset rows. Results depend on the pages and responses Threads makes available; login walls, rate limits, and upstream changes can limit or change coverage.

Inputs

• startUrls: HTTPS Threads post or profile URLs. mode: "auto" routes them by URL; bfs extracts replies from a post; profile reads profile metadata/posts.
• search: Keyword to search for posts; use mode: "search" or auto with no URLs.
• maxItems: Maximum output rows (default 100).
• includeNestedReplies: Request deeper reply traversal in BFS mode; deeper traversal can increase runtime and output charges.
• cookies: Optional Playwright cookie-object array. Use only a session you control and content you are authorized to access. Apify marks this input secret/encrypted. Cookies are not written to actor logs.
• proxy: Optional Apify proxy configuration. It may help with access limits but does not guarantee access.

Output

Rows identify their kind with item_type and include only fields available in the source response. Engagement values, timestamps, IDs, and URLs are not fabricated when missing. See .actor/dataset_schema.json for the output fields.

Pricing

• Output event: currently $0.0015 per dataset item.
• Start event: currently $0.05 per allocated GB (minimum one event); the 2 GB default is $0.10 before any account-tier discount.
• Verify the current Apify pricing panel before each run; pricing and account discounts can change.

Notes

• Threads can change page behavior and response formats without notice; a code update may be needed after upstream changes.
• A public profile summary is not the same as a complete profile history. The Actor only returns data it can extract from the responses available to the run.
• Empty input exits cleanly with a warning. Malformed or unsupported URLs exit with a warning and no dataset; only HTTPS Threads post/profile URLs are accepted.