Threads Posts by user API
API health
- 24h health
- Normal
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
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.
Send POST https://api.everyinfra.com/api/v1/social with platform set to threads and action set to user_posts. Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
#Please help me write a data collection script with the EveryInfra Threads Posts by user endpoint (threads/user_posts).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to threads and action to user_posts, and put the parameters inside params.
- Required parameters:
- username: 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.
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 10)
- Returns a list of records. Main fields of each record: id, code, url, text, author_username, author_name, author_is_verified, like_count, comment_count, repost_count, quote_count, share_count; 17 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=threads.
- Example request body:
{
"platform": "threads",
"action": "user_posts",
"params": {
"username": "zuck"
}
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
#| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | threads | Platform identifier, fixed value. |
action | body | string | Yes | user_posts | Capability identifier, fixed value. |
username | body.params | string | Yes | - | 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. |
limit | body.params | integer (1–50) | No | 10 | The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
Code samples
#curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "threads",
"action": "user_posts",
"params": {
"username": "zuck"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
#{ "id": "req_…", "platform": "threads", "action": "user_posts", "results": [ { "id": "•••", "code": "Ddt7cL5EfUG", "url": "https://www.threads.com/@zuck/post/Ddt7cL5EfUG", "text": "Agrippa said it's time to get back to work 😎", "author_username": "zuck", "author_name": "•••", "author_is_verified": true, "like_count": 3245, "comment_count": 294, "repost_count": 180, "quote_count": 29, "posted_at": "2026-09-25T16:50:21+00:00", "platform": "threads", "media_type": "image" }, { "id": "•••", "code": "Ddpj4YZkd3P", "url": "https://www.threads.com/@zuck/post/Ddpj4YZkd3P", "text": "Here's everything I announced at Meta Connect today 👇", "author_username": "zuck", "author_name": "•••", "author_is_verified": true, "like_count": 2644, "comment_count": 597, "repost_count": 159, "quote_count": 34, "posted_at": "2026-09-24T00:07:31+00:00", "platform": "threads" } ], "count": 7, "billing": { "charged": …, "charged_usd": …, "balance_after_usd": …, … }, "quota": { … }}
Response fields
#Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
code | Keeps the platform's own meaning |
url | Link to the record on the platform. |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
author_username | Author's username (@handle), usually usable in URLs. |
author_name | Author's display name. |
author_is_verified | Keeps the platform's own meaning |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
comment_count | Comments. null means not disclosed, not 0. |
repost_count | Reposts (as distinct from quote posts). null means not disclosed. |
quote_count | Keeps the platform's own meaning |
share_count | Shares. null means not disclosed, not 0. |
view_count | Views or plays. null means not disclosed, not 0. |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
media_type | Keeps the platform's own meaning |
hashtags | Hashtags in the text, in order of appearance; absent when there are none. |
mentions | Keeps the platform's own meaning |
Errors and billing
#- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.
Official references
#Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- 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 2026-09-04