Platform availability
- 24h health
- Normal
Last 30 days
Available capabilities
Each Threads action, what it does, its price and its health over the last 24 hours. Open an action for its parameters, response fields and code samples.
| Capability | What it does | Per 1,000 | 24-hour health |
|---|---|---|---|
Searchsearch | Pull Threads posts that mention a keyword, with each post's text, author, like and comment counts and publish time. | $0.56 per 1,000 requests | Normal |
Profilesprofile | Check a Threads account's display name, bio, follower count, external link and verification and privacy flags from its handle. | $0.56 per 1,000 requests | Normal |
Posts by useruser_posts | List posts from a Threads account with separate like, comment, repost, quote, share and view counts, plus hashtags and mentions. | $0.56 per 1,000 requests | Normal |
Post detailspost_detail | Read a single Threads post from its full URL, with text, author, engagement counts, hashtags, media and a paid partnership flag. | $0.56 per 1,000 requests | Normal |
Commentscomments | Collect the replies under a Threads post, each with text, author, verification, like count and what it responds to. | $0.56 per 1,000 requests | Normal |
Profile discoverydiscover_profiles | Discover Threads creator profiles related to a keyword, with bio, follower count, verification, external links and any listed emails or phone numbers. | $0.56 per 1,000 requests | Normal |
Followersfollowers | Get a Threads account's follower, following, post and like counts, with a precision flag that marks rounded figures. | $0.56 per 1,000 requests | Normal |
Open a capability for its parameters, response fields, code samples and trial.
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.
| Action | Required | Optional | Delivery | Limit | Per 1,000 | Response fields |
|---|---|---|---|---|---|---|
searchSearch Pull Threads posts that mention a keyword, with each post's text, author, like and comment counts and publish time. It does not look up profiles by name, and it promises neither full history nor real-time coverage. | 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 Check a Threads account's display name, bio, follower count, external link and verification and privacy flags from its handle. Pass the handle with or without the @, not a profile URL; private profiles are not opened. | 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 · external_url |
user_postsPosts by user List posts from a Threads account with separate like, comment, repost, quote, share and view counts, plus hashtags and mentions. Pass the handle, not a profile URL; one batch may not cover the full history and leaves out the account's replies. | 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 · media_type · hashtags · mentions |
post_detailPost details Read a single Threads post from its full URL, with text, author, engagement counts, hashtags, media and a paid partnership flag. It returns the post alone, not the full thread around it. | 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 · media_url · hashtags |
commentsComments Collect the replies under a Threads post, each with text, author, verification, like count and what it responds to. Pass the full post URL; nested replies may not all come back. | 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 Discover Threads creator profiles related to a keyword, with bio, follower count, verification, external links and any listed emails or phone numbers. It runs as an async job, so read the finished result rather than the first status reply; a match proves neither identity nor fit. | 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 · emails · phones · external_links |
followersFollowers Get a Threads account's follower, following, post and like counts, with a | 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 do the Threads search parameters mean?
Pull Threads posts that mention a keyword, with each post's text, author, like and comment counts and publish time. It does not look up profiles by name, and it promises neither full history nor real-time coverage.
Full API reference: parameters, code samples, response example and health →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 Metrics — Meta 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?
Check a Threads account's display name, bio, follower count, external link and verification and privacy flags from its handle. Pass the handle with or without the @, not a profile URL; private profiles are not opened.
Full API reference: parameters, code samples, response example and health →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 Constraints — Meta 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?
List posts from a Threads account with separate like, comment, repost, quote, share and view counts, plus hashtags and mentions. Pass the handle, not a profile URL; one batch may not cover the full history and leaves out the account's replies.
Full API reference: parameters, code samples, response example and health →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 Username — Meta 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?
Read a single Threads post from its full URL, with text, author, engagement counts, hashtags, media and a paid partnership flag. It returns the post alone, not the full thread around it.
Full API reference: parameters, code samples, response example and health →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 Shares — Meta 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?
Collect the replies under a Threads post, each with text, author, verification, like count and what it responds to. Pass the full post URL; nested replies may not all come back.
Full API reference: parameters, code samples, response example and health →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 Trees — Meta 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 Replies — Meta 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?
Discover Threads creator profiles related to a keyword, with bio, follower count, verification, external links and any listed emails or phone numbers. It runs as an async job, so read the finished result rather than the first status reply; a match proves neither identity nor fit.
Full API reference: parameters, code samples, response example and health →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 Search — Meta 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. It is not guaranteed to filter discovered profiles, 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 search has no date filter.
What do the Threads followers parameters mean?
Get a Threads account's follower, following, post and like counts, with a precision flag that marks rounded figures. It returns counts only, with no list of who follows the account and no trend over time.
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 Constraints — Meta 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 action runs asynchronously.
- 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 guides
Worked examples and methods built on these actions. Check the current actions, parameters and fields on this page first; an article's examples and limits do not replace the live catalog.
Multiplatform Reputation Monitoring Blueprint: Define Scope Before Evaluating Negative Shifts
Design a traceable reputation monitoring workflow starting with target lists, comment identities, and incremental cursors; use offline samples to demonstrate deduplication and ingestion gaps while preserving manual review.
Read the article →Unified Data API Getting Started: From Capability Catalog to First Available Result
Access multi-platform data using platform, action, and params: read the capability catalog, complete minimal requests, handle asynchronous tasks, partial results, and billing, and establish traceable data records.
Read the article →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.
Does Threads have an official API?
Yes. Meta's Threads API is built for publishing and managing a user's own Threads posts. Searching public posts by keyword and reading public profiles need the threads_keyword_search and threads_profile_discovery permissions, which require Meta App Review and come with per-user limits of 2,200 searches and 1,000 profile lookups per 24 hours.
Official sources: Meta: Threads keyword search · Meta: Threads API overview · Checked
Do I need a Threads developer account or API key?
No. Requests go through EveryInfra with an EveryInfra API key: sign up, create a key in the console and send it as Authorization: Bearer <API_KEY>. You do not register a Threads developer app, apply for Threads API access or sign in with a Threads account, and the actions return public Threads data only.
How much does the Threads API cost per 1,000 requests?
$0.56 per 1,000 requests, depending on the action; each action's price is listed in the table on this page and in the public catalog. There is no subscription: you top up a USD balance and pay per call, and failed calls and empty results are not charged.
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 record, and every other action has its own field list.
Does every Threads action return immediately?
Actions labeled asynchronous return a job ID you poll. Every other action can also run asynchronously: add "mode": "async" to the request body to receive a job ID immediately, useful for slow tasks or large limits. The current catalog contains sync delivery and async delivery.