Threads Details API

POST

API health

24h health
Normal
24h average time
—
Last checked
September 26, 2026 at 18:04 (UTC)
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Health APINormal
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)StatusHealthAverage time
2026-09-26 18:00 - 18:59Normal——
2026-09-26 17:00 - 17:59Normal——
2026-09-26 16:00 - 16:59Normal——
2026-09-26 15:00 - 15:59Normal——
2026-09-26 14:00 - 14:59Normal——
2026-09-26 13:00 - 13:59Normal——
2026-09-26 12:00 - 12:59Normal——
2026-09-26 11:00 - 11:59Normal——
2026-09-26 10:00 - 10:59Normal——
2026-09-26 09:00 - 09:59Normal——
2026-09-26 08:00 - 08:59Normal——
2026-09-26 07:00 - 07:59Normal——
2026-09-26 06:00 - 06:59Normal——
2026-09-26 05:00 - 05:59Normal——
2026-09-26 04:00 - 04:59Normal——
2026-09-26 03:00 - 03:59Normal——
2026-09-26 02:00 - 02:59Normal——
2026-09-26 01:00 - 01:59Normal——
2026-09-26 00:00 - 00:59Normal——
2026-09-25 23:00 - 23:59Normal——
2026-09-25 22:00 - 22:59Normal——
2026-09-25 21:00 - 21:59Normal——
2026-09-25 20:00 - 20:59Normal——
2026-09-25 19:00 - 19:59Normal——
2026-09-26Normal——
2026-09-25Normal——
2026-09-24Normal——
2026-09-23Normal——
2026-09-22Normal——
2026-09-21Normal——
2026-09-20Normal——
2026-09-19Normal——
2026-09-18Normal——
2026-09-17Normal——
2026-09-16Normal——
2026-09-15Normal——
2026-09-14Normal——
2026-09-13Normal——
2026-09-12Normal——
2026-09-11Normal——
2026-09-10Normal——
2026-09-09Normal——
2026-09-08Normal——
2026-09-07Normal——
2026-09-06Normal——
2026-09-05Normal——
2026-09-04Normal——
2026-09-03Normal——
2026-09-02Normal——
2026-09-01Normal——
2026-08-31Normal——
2026-08-30Normal——
2026-08-29Normal——
2026-08-28Normal——

Retrieve public profile details from Threads. Accepts these parameters: username. Returns these fields: username, is_verified, bio, and display_name.

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

NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYesthreadsPlatform identifier, fixed value.
actionbodystringYesprofileCapability identifier, fixed value.
usernamebody.paramsNot declaredYes-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.

Code samples

bash
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": "profile",
  "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

Real response

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. id, billing and quota differ on every call, so only their shape is shown.

json
{
  "id": "req_…",
  "platform": "threads",
  "action": "profile",
  "results": {
    "user_id": "(已隐去)",
    "username": "zuck",
    "display_name": "(已隐去)",
    "bio": "Mostly superintelligence and MMA takes",
    "follower_count": 5744623,
    "is_verified": true,
    "is_private": false,
    "url": "https://www.threads.net/@zuck",
    "avatar_url": "https://instagram.fbau6-1.fna.fbcdn.net/(已隐去)",
    "platform": "threads"
  },
  "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.

FieldMeaning
user_idUser's unique ID on the source platform.
usernameUsername (@handle).
display_nameDisplay name; can differ from username.
bioProfile bio written by the account; may contain line breaks and emoji.
follower_countFollowers. null means not disclosed, not 0.
is_verifiedWhether the platform verified the account. null means it cannot be determined.
is_privateKeeps the platform's own meaning
urlLink to the record on the source platform.
avatar_urlAvatar image link. Some platforms return sized CDN links that can expire.
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).
external_urlKeeps 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: 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 2026-09-04