Threads Posts by user API
API health
- 24h health
- Normal
- 24h average time
- —
- Last checked
- September 26, 2026 at 18:04 (UTC)
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
How health is measured
- Health = the share of calls that returned data, in percent. Empty results, failures and unknown outcomes do not count as returning data.
- Levels: 90% and above is healthy, 70% and above is available, 40% and above is limited; anything lower is mostly down.
- A period (the last 24 hours, one hour or one day) gets a score only once it has at least 50 calls. Periods with fewer calls show as normal: a few failures among a handful of calls do not mean the API is down.
- Calls include real customer calls and our own daily probe calls. Request errors (wrong parameters, no balance) are excluded.
- Average time counts only calls that completed normally: response time for sync calls, acceptance to completion for async ones.
By period
| Time (UTC) | Status | Health | Average time |
|---|---|---|---|
| 2026-09-26 18:00 - 18:59 | Normal | — | — |
| 2026-09-26 17:00 - 17:59 | Normal | — | — |
| 2026-09-26 16:00 - 16:59 | Normal | — | — |
| 2026-09-26 15:00 - 15:59 | Normal | — | — |
| 2026-09-26 14:00 - 14:59 | Normal | — | — |
| 2026-09-26 13:00 - 13:59 | Normal | — | — |
| 2026-09-26 12:00 - 12:59 | Normal | — | — |
| 2026-09-26 11:00 - 11:59 | Normal | — | — |
| 2026-09-26 10:00 - 10:59 | Normal | — | — |
| 2026-09-26 09:00 - 09:59 | Normal | — | — |
| 2026-09-26 08:00 - 08:59 | Normal | — | — |
| 2026-09-26 07:00 - 07:59 | Normal | — | — |
| 2026-09-26 06:00 - 06:59 | Normal | — | — |
| 2026-09-26 05:00 - 05:59 | Normal | — | — |
| 2026-09-26 04:00 - 04:59 | Normal | — | — |
| 2026-09-26 03:00 - 03:59 | Normal | — | — |
| 2026-09-26 02:00 - 02:59 | Normal | — | — |
| 2026-09-26 01:00 - 01:59 | Normal | — | — |
| 2026-09-26 00:00 - 00:59 | Normal | — | — |
| 2026-09-25 23:00 - 23:59 | Normal | — | — |
| 2026-09-25 22:00 - 22:59 | Normal | — | — |
| 2026-09-25 21:00 - 21:59 | Normal | — | — |
| 2026-09-25 20:00 - 20:59 | Normal | — | — |
| 2026-09-25 19:00 - 19:59 | Normal | — | — |
| 2026-09-26 | Normal | — | — |
| 2026-09-25 | Normal | — | — |
| 2026-09-24 | Normal | — | — |
| 2026-09-23 | Normal | — | — |
| 2026-09-22 | Normal | — | — |
| 2026-09-21 | Normal | — | — |
| 2026-09-20 | Normal | — | — |
| 2026-09-19 | Normal | — | — |
| 2026-09-18 | Normal | — | — |
| 2026-09-17 | Normal | — | — |
| 2026-09-16 | Normal | — | — |
| 2026-09-15 | Normal | — | — |
| 2026-09-14 | Normal | — | — |
| 2026-09-13 | Normal | — | — |
| 2026-09-12 | Normal | — | — |
| 2026-09-11 | Normal | — | — |
| 2026-09-10 | Normal | — | — |
| 2026-09-09 | Normal | — | — |
| 2026-09-08 | Normal | — | — |
| 2026-09-07 | Normal | — | — |
| 2026-09-06 | Normal | — | — |
| 2026-09-05 | Normal | — | — |
| 2026-09-04 | Normal | — | — |
| 2026-09-03 | Normal | — | — |
| 2026-09-02 | Normal | — | — |
| 2026-09-01 | Normal | — | — |
| 2026-08-31 | Normal | — | — |
| 2026-08-30 | Normal | — | — |
| 2026-08-29 | Normal | — | — |
| 2026-08-28 | Normal | — | — |
Retrieve public posts from Threads. Accepts these parameters: username. Returns these fields: quote_count, hashtags, author_username, and author_is_verified.
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.
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 | Not declared | 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 |
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
Captured September 26, 2026 at 08:56 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.
{
"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": { … },
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the source does not provide are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the source 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 source platform. |
text | Body text with HTML removed. Long text may be truncated. |
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 | Keeps the platform's own meaning |
mentions | Keeps the platform's own meaning |
Errors and billing
- 401
- Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
- 422
- Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
- 402
- Insufficient balance. Top up first.
- 429
- Per-minute request limit reached. Wait for Retry-After and try again.
- 503
- Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
- 200 empty
- The request completed without data and is not charged (billing.reason = empty_result_refunded).
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