Threads
Pricing
from $2.00 / 1,000 results
Threads
Collect or Search for Posts and User profiles on Threads. It's fast and costs little!
Pricing
from $2.00 / 1,000 results
Rating
1.0
(2)
Developer
Canadesk Support
Maintained by CommunityActor stats
19
Bookmarked
377
Total users
9
Monthly active users
5.4 hours
Issues response
15 hours ago
Last modified
Categories
Share
Collect public profiles, posts, replies, reposts and search results from Threads. Run one profile or search term, or submit up to 100 inputs in one batch.
Features
| Process | What you get |
|---|---|
| Get User Profile | Username, name, biography, follower count, verification status, profile image and website, when available. |
| Get User Posts | Recent posts with text, links, dates and engagement counts, plus the account's profile. |
| Get User Replies | The account's public replies with the original post and author for context. |
| Get User Reposts | Posts shared by the account, plus its profile. |
| Search for User | Public accounts matching your search terms. |
| Search | Public posts matching a keyword or phrase. |
Results include the text, timestamps, links, engagement counts and profile fields available in the public response. Posts and search use the initial response; they do not provide a complete account archive.
Getting started
- Select a process, such as Get User Posts.
- Add one or more usernames or profile URLs, such as
microsoft365andhttps://www.threads.com/@spotify/. For searches, enter keywords or phrases instead. - Set the maximum posts or matches per query. Optionally choose the newest posts first or enter a Since date.
- Start the Actor, then open the dataset to review or download your results.
Both threads.com and threads.net profile URLs are supported. Use usernames or profile URLs rather than numeric profile IDs.
Example: collect posts from two profiles
{"process": "gt","keyword": ["microsoft365", "https://www.threads.com/@spotify/"],"maximum": 25,"sort": "recent","includeraw": "yes","proxy": { "useApifyProxy": true }}
To search posts, use "process": "st" and enter search phrases in keyword. The other process values are gu (profile), gi (replies), go (reposts) and su (user search).
Filters and options
| Option | How to use it |
|---|---|
| Profiles or search terms | Add multiple entries to collect them in one run; up to 10,000 entries are accepted. |
| Maximum posts or matches | Choose the result limit per query; the default is 25. A returned profile is additional. |
| Sorting | Keep pinned posts first or sort from newest to oldest. |
| Since date | Enter YYYY-MM-DD to exclude older posts from the available results. |
| Raw data | Include additional profile, post and media fields. |
| Proxy configuration | Use the preselected Apify proxy or provide your own. |
Your results
Profile results include identifying information and available account details. Post results include id, url, text, date, timestamp, and available counts for likes, replies, reposts, quotes and shares. Reply results also include the original author and reply content.
With pay-per-event pricing, each profile, post, reply entry, repost or user-search match is a separate result. Embedded author details and reply context are included in that result.
Pricing
Each valid pay-per-event run with at least one input includes a minimum charge of 100 result units, shared across all inputs in that run. Any placeholder rows are clearly marked and contain no scraped data; filter them out when exporting. Each separate run has its own minimum, including scheduled or API runs. Platform usage is included.
Export rows with rowType: result to include only collected data. A minimum already charged still applies if lookups fail or the run is stopped; interrupted runs may contain fewer rows.
Until a scheduled switch to pay-per-event takes effect, existing rental pricing and the grouped {profile, data} output remain active, without placeholders.
Availability
Threads exposes a limited recent window through its public website. The Actor cannot guarantee complete post history or the requested number of results. Private or unavailable profiles may return no data. For ongoing monitoring, schedule regular runs and use the date filter to focus on recent posts.
Support
Open an issue on the Actor's Issues tab and include your run URL and the profiles or search terms involved.
Unsuccessful lookups
If a lookup problem prevents a run from returning any real results, the run returns one clear error record and applies a reduced minimum of $0.02 at the current rate, plus the listed start fee.