EveryData platform API
Threads API
Threads profiles, posts, comments, profile discovery, and follower counts are the Threads objects documented here; 7 actions including `search`, `profile`, `user_posts` keep Threads selectors and outputs separate.
On Threads, `search` handles matching public results through `keyword`, while `profile` handles the selected public record through `username`; neither Threads action receives undeclared filters.
- Endpoint
- POST /api/v1/social
- Capabilities
- 7
- Per 1,000
- $0.556
Available capabilities
Compare the Threads actions by required input, returned data, and price. Use the action identifier exactly as shown in your request.
| Action | Required | Optional | Delivery | Limit | Per 1,000 | Response fields |
|---|---|---|---|---|---|---|
searchSearch Search public results on Threads. Accepts these parameters: | keyword | — | Sync delivery | Catalog values: defaultLimit=15, maxLimit=50. A limit can control pages or per-parent expansion for some actions, so it is not always a final row count. | $0.56 per 1,000 requests | id · url · text · author_name · author_username · author_id · like_count · comment_count · posted_at · platform |
profileProfiles Retrieve public profile details from Threads. Accepts these parameters: | username | — | Sync delivery | — | $0.56 per 1,000 requests | user_id · username · display_name · bio · follower_count · is_verified · is_private · url · avatar_url · platform |
user_postsPosts by user Retrieve public posts from Threads. Accepts these parameters: | username | — | Sync delivery | Catalog values: defaultLimit=10, maxLimit=50. A limit can control pages or per-parent expansion for some actions, so it is not always a final row count. | $0.56 per 1,000 requests | id · code · url · text · author_username · author_name · author_is_verified · like_count · comment_count · repost_count · quote_count · share_count · view_count · posted_at · platform |
post_detailPost details Retrieve post details from Threads. Accepts these parameters: | url | — | Sync delivery | — | $0.56 per 1,000 requests | id · code · url · text · author_username · author_name · author_is_verified · like_count · comment_count · repost_count · quote_count · share_count · view_count · posted_at · is_paid_partnership · platform |
commentsComments Retrieve public comments from Threads. Accepts these parameters: | url | — | Sync delivery | — | $0.56 per 1,000 requests | id · url · text · author_username · author_name · author_is_verified · like_count · comment_count · reply_to · posted_at · platform |
discover_profilesProfile discovery Use the | keyword | since, until | Async delivery | Catalog values: defaultLimit=10, maxLimit=50. A limit can control pages or per-parent expansion for some actions, so it is not always a final row count. | $0.56 per 1,000 requests | username · display_name · bio · follower_count · is_verified · url · avatar_url · platform |
followersFollowers Retrieve public follower metrics from Threads. Accepts these parameters: | username | channel | Sync delivery | — | $0.56 per 1,000 requests | id · username · url · follower_count · following_count · post_count · like_count · connection_count · precision · platform |
What does each Threads action accept?
Each answer below pairs one callable action with its real inputs. Parameter meanings and allowed values are action-specific; a familiar name does not carry the same meaning across every platform.
Official sources are linked only to clarify the platform term beside them. They do not imply platform authorization or endorsement, and they do not add official-site features to the EveryInfra API contract.
What do the Threads search parameters mean?
Search public results on Threads. Accepts these parameters: keyword. Returns these fields: author_id, comment_count, posted_at, and author_name.
keywordRequired- Specifies the search query to find public posts using search or creator profiles using discover_profiles. The discover_profiles action operates asynchronously, so the initial task status response must not be parsed as the final creator list.Official Meta Documentation: Threads Keyword Discovery and Engagement MetricsMeta official sources define public post discovery using search keywords and distinguish between replies, reposts, quotes, and off-platform shares. This defines Threads product objects and terminology, but does not indicate that this API endpoint supports all official filtering, write, or analytics capabilities.Checked
What do the Threads profile parameters mean?
Retrieve public profile details from Threads. Accepts these parameters: username. Returns these fields: user_id, follower_count, display_name, and avatar_url.
usernameRequired- Specifies the Threads handle (with or without @) for profile, user_posts, and followers actions. The profile and user_posts actions do not accept full profile URLs. The followers action returns aggregate follower counts rather than a user member list.Official Meta Documentation: Threads Profiles, Follower Counts, and Access ConstraintsMeta official sources define `username`, display name, bio, and `follower_count`, noting that public profile discovery requires specific permissions, standard access is restricted to select official accounts, and public account/follower thresholds apply. Referenced here strictly to explain platform terminology, this does not imply that this API holds those permissions or matches official endpoint capabilities.Checked
What do the Threads user_posts parameters mean?
Retrieve public posts from Threads. Accepts these parameters: username. Returns these fields: code, author_name, share_count, and posted_at.
usernameRequired- Specifies the Threads handle (with or without @) for profile, user_posts, and followers actions. The profile and user_posts actions do not accept full profile URLs. The followers action returns aggregate follower counts rather than a user member list.Official Meta Documentation: Locating Threads Posts by UsernameMeta official sources distinguish user profile endpoints from user post endpoints, detailing how `profile_posts` locates posts by exact username while listing distinct fields such as `id`, `shortcode`, and `permalink`. Official `access_token`, pagination, and date parameters must not be assumed to be supported by this API endpoint.Checked
What do the Threads post_detail parameters mean?
Retrieve post details from Threads. Accepts these parameters: url. Returns these fields: repost_count, is_paid_partnership, author_name, and share_count.
urlRequired- Specifies the full post URL (e.g., https://www.threads.com/@username/post/POST_CODE) for post_detail and comments actions. The comments action does not guarantee extraction of all nested comment threads.Official Meta Documentation: Threads Reposts, Quotes, and Off-Platform SharesMeta official sources separate reposts, quotes, and shares, defining shares specifically as off-platform sharing. This clarifies original post engagement metrics, but does not guarantee that every metric will be present in every response or that publishing actions are supported.Checked
What do the Threads comments parameters mean?
Retrieve public comments from Threads. Accepts these parameters: url. Returns these fields: reply_to, like_count, author_name, and posted_at.
urlRequired- Specifies the full post URL (e.g., https://www.threads.com/@username/post/POST_CODE) for post_detail and comments actions. The comments action does not guarantee extraction of all nested comment threads.Official Meta Documentation: Top-Level Replies vs. Full Conversation TreesMeta official sources distinguish top-level replies from full, unlimited-depth conversations, defining `replied_to` as the direct parent content ID. In this API, `reply_to` represents the replied-to username rather than the official `replied_to` field and does not guarantee a full comment tree; official visibility and copyright restrictions may also cause missing fields.CheckedOfficial Meta Documentation: Permissions Required to Read Threads RepliesMeta official documentation for reply management focuses on an account's own Threads, requiring an appropriate access token and read permissions. Referencing this does not guarantee access to arbitrary third-party posts nor prove that this product has received platform authorization.Checked
What do the Threads discover_profiles parameters mean?
Use the discover_profiles action on Threads. Accepts these parameters: keyword, until, and since. Returns these fields: display_name, avatar_url, follower_count, and is_verified.
keywordRequired- Specifies the search query to find public posts using search or creator profiles using discover_profiles. The discover_profiles action operates asynchronously, so the initial task status response must not be parsed as the final creator list.Official Meta Documentation: Public Profile Discovery Is Not Exact Keyword User SearchMeta official `profile_lookup` requires an exact username and is subject to permissions, access levels, and account qualifications. Candidate profile discovery by keyword in this API must not be treated as equivalent to official exact lookups, nor does official documentation guarantee coverage of all users.Checked
sinceOptional- Provides a shared lower date bound parameter for discover_profiles. Whether this filter is actively applied during profile discovery is unconfirmed, and it does not filter account creation dates.
untilOptional- Provides a shared upper date bound parameter for discover_profiles. It does not guarantee complete coverage of creators from that period and is not available as a date filter on the primary search action.
What do the Threads followers parameters mean?
Retrieve public follower metrics from Threads. Accepts these parameters: username and channel. Returns these fields: precision, following_count, connection_count, and like_count.
usernameRequired- Specifies the Threads handle (with or without @) for profile, user_posts, and followers actions. The profile and user_posts actions do not accept full profile URLs. The followers action returns aggregate follower counts rather than a user member list.Official Meta Documentation: Threads Profiles, Follower Counts, and Access ConstraintsMeta official sources define `username`, display name, bio, and `follower_count`, noting that public profile discovery requires specific permissions, standard access is restricted to select official accounts, and public account/follower thresholds apply. Referenced here strictly to explain platform terminology, this does not imply that this API holds those permissions or matches official endpoint capabilities.Checked
channelOptional- Provides a compatibility fallback for specifying an account handle in the followers action. It takes lower precedence than username and returns follower counts rather than channel or group member lists.
How to use the Threads API
- 01Read the public catalog and choose a platform action.
- 02Send the platform, action, and required parameters to POST /api/v1/social.
- 03Handle a synchronous result or poll the returned job ID when the selected action is asynchronous.
- 04Store the structured response fields needed by your application.
curl -X POST https://api.everyinfra.com/api/v1/social \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"platform":"threads","action":"search","params":{"keyword":"<keyword>"}}'
Threads API questions
What can I retrieve with the Threads API?
Set platform to threads. The current catalog lists search, profiles, posts by user, post details, comments, and more. These action names identify different Threads objects or views; they are not interchangeable search modes.
Which input starts a Threads `search` request?
Specifies the search query to find public posts using search or creator profiles using discover_profiles. The discover_profiles action operates asynchronously, so the initial task status response must not be parsed as the final creator list. Send it as keyword inside params.
Which fields can Threads `search` return?
Its declared schema includes text, author_name, author_username, and author_id. A declared field can still be absent from an individual source record, and every other action has its own field list.
Does every Threads action return immediately?
No assumption is needed: this page labels each action's delivery mode. The current catalog contains sync delivery and async delivery; poll a returned job ID only for an action labeled asynchronous.