# Threads Details API (threads.profile)

- Canonical page: https://everyinfra.com/en/threads-api/profile
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "threads", "action": "profile", "params": {...}}
- Price: $0.000556 per call ($0.56 per 1,000 requests); failed calls and empty results are not charged
- Returns: single object
- Mode: sync; add "mode": "async" for slow tasks

Threads Details reads the public profile of one Threads account from its handle and returns a single record: `user_id`, handle, display name, bio, follower count, verification and privacy flags, the profile link and the avatar. Creator marketers and social researchers use it to confirm who is behind a handle and how large the audience is, to vet creators before a campaign, or to keep a dated record of follower counts for the accounts they track.

`username` is the handle alone, with or without the @, because this capability does not parse full profile links. `display_name` can differ from the handle, and `bio` is the account's own text, which may include line breaks and emoji, so normalize it before keyword matching. A null `follower_count` signals an undisclosed number, not an empty audience. `avatar_url` can be a sized link that expires, so download the image if you need to keep it.

## Health

- Live health (24h percent, hourly and daily trends): https://api.everyinfra.com/api/v1/social/availability?platform=threads&action=profile

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| username | not declared | yes | not declared | 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. |

## Response fields (items in `results`)

| field | meaning |
|---|---|
| user_id | User's unique ID on the platform. |
| username | Username (@handle). |
| display_name | Display name; can differ from username. |
| bio | Profile bio written by the account; may contain line breaks and emoji. |
| follower_count | Followers. null means not disclosed, not 0. |
| is_verified | Whether the platform verified the account. null means it cannot be determined. |
| is_private | platform-native meaning |
| url | Link to the record on the platform. |
| avatar_url | Avatar image link. Some platforms return sized CDN links that can expire. |
| platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
| external_url | platform-native meaning |

## Example

```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"
  }
}'
```

```python
import os
import requests

response = requests.post(
    "https://api.everyinfra.com/api/v1/social",
    headers={"Authorization": f"Bearer {os.environ['EVERYINFRA_API_KEY']}"},
    json={
        "platform": "threads",
        "action": "profile",
        "params": {
            "username": "zuck",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

Real response to the example request above, captured 2026-09-26T08:56:04Z. `results` and `count` are real 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.

```text
{
  "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": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}
```

## FAQ

### Can I pass a threads.net or threads.com profile link?

No. Send only the handle, the part after the @ in a link such as threads.com/@zuck, so zuck or @zuck. This capability does not parse full profile URLs from either domain, and a display name does not identify the account either.

### How do I tell verified and private accounts apart?

`is_verified` is true for accounts Threads has verified; null means the check could not be made, which is different from false. `is_private` is true when the account keeps its posts private: the profile still comes back, but its posts are not public.

### How do I read the account's posts?

Pass the same handle to the Threads Posts by user capability, which, like this one, takes the handle rather than a profile link. For a single post you already have a link to, the Threads Post details capability takes the full post URL, shaped like threads.com/@<handle>/post/<code>.

## Also

- Capability catalog (no key): https://api.everyinfra.com/api/v1/social/catalog?platform=threads
- OpenAPI: https://everyinfra.com/openapi.json · Agents guide: https://everyinfra.com/agents.md