Threads Followers API

POST

API health

24h health: Normal

Healthy / normal
Available
Limited
Mostly down

Last 24 hours

Last 30 days

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.

Send POST https://api.everyinfra.com/api/v1/social with platform set to threads and action set to followers. 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 Followers endpoint (threads/followers).

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 followers, 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:
- channel: 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.
- Returns one object. Main fields: id, username, url, follower_count, following_count, post_count, like_count, connection_count, precision.
- Example request body:
{
"platform": "threads",
"action": "followers",
"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	`followers`	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.
`channel`	body.params	`string`	No	-	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.

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": "followers",
  "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

json

{  "id": "req_…",  "platform": "threads",  "action": "followers",  "results": {    "id": "zuck",    "username": "zuck",    "url": "https://www.threads.com/•••",    "follower_count": 5744625,    "precision": "exact",    "platform": "threads"  },  "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.
`username`	Username (@handle).
`url`	Link to the record on the platform.
`follower_count`	Followers. null means not disclosed, not 0.
`following_count`	Accounts followed. null means not disclosed, not 0.
`post_count`	Total posts. null means not disclosed, not 0.
`like_count`	Likes. null means the platform or this capability does not disclose it; it is not 0.
`connection_count`	Keeps the platform's own meaning
`precision`	Keeps the platform's own meaning
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

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.

Errors

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