# Bluesky Details API (bluesky.profile)

- Canonical page: [https://everyinfra.com/en/bluesky-api/profile](https://everyinfra.com/en/bluesky-api/profile?utm_medium=ai_doc&utm_campaign=page_md)
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "bluesky", "action": "profile", "params": {...}}
- Price: $0.001389 per call ($1.39 per 1,000 requests); failed calls and empty results are not charged
- Returns: single object
- Mode: sync; add "mode": "async" for slow tasks

Bluesky Details reads one Bluesky account's public profile from its full handle and returns a single record: `user_id`, handle, display name, bio, avatar and banner images, follower, following and post counts, the verification flag and the date the account joined. Journalists, researchers and community managers use it to check who runs an account and how big it is before citing, following or partnering with it, or to keep a dated log of audience size for accounts they watch.

`username` must be the complete handle, such as alice.bsky.social, or the custom domain an account uses as its handle. `joined_at` dates the account's registration, which helps you spot newly created accounts. When a count comes back null, Bluesky did not disclose it, so record it as missing rather than as zero.

## Health

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

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| username | not declared | yes | not declared | Specifies a complete Bluesky handle, such as alice.bsky.social or a connected custom domain name. Do not pass a display nickname or a bsky.app/profile/ page URL. The profile, user_posts, followers, and following actions all use this parameter to locate the target account. |

## 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. |
| url | Link to the record on the platform. |
| avatar_url | Avatar image link. Some platforms return sized CDN links that can expire. |
| is_verified | Whether the platform verified the account. null means it cannot be determined. |
| joined_at | platform-native meaning |
| source_username | platform-native meaning |
| platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
| banner_url | platform-native meaning |
| 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. |

## 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": "bluesky",
  "action": "profile",
  "params": {
    "username": "<HANDLE>.bsky.social"
  }
}'
```

```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": "bluesky",
        "action": "profile",
        "params": {
            "username": "<HANDLE>.bsky.social",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

No real sample for these example parameters yet: structure only, every value is a placeholder (…).

```text
{
  "id": "req_…",
  "platform": "bluesky",
  "action": "profile",
  "results": {
    "user_id": …,
    "username": …,
    "display_name": …,
    "bio": …,
    "url": …,
    "avatar_url": …,
    "is_verified": …,
    "joined_at": …,
    "source_username": …,
    "platform": …,
    "banner_url": …,
    "follower_count": …,
    "following_count": …,
    "post_count": …
  },
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}
```

## FAQ

### Do I need a Bluesky API key or app password?

No. You call it with your EveryInfra API key, and the request carries one input, `username`, the account's full handle. It has no field for Bluesky credentials, so you never hand over a Bluesky login or app password to read a public profile.

### Where do I find the full handle?

On the profile it is shown after the @, and it is also the last part of a link such as bsky.app/profile/<handle>. Copy just the handle, and do not pass the link or the display name. An account that uses its own domain as its handle has no .bsky.social suffix, so do not add one.

### Which input do the other Bluesky capabilities use?

The same full handle. Bluesky Posts by user, Followers and Following all locate the account by `username` in the same form, so the value you send here can be reused unchanged to read the account's posts or its follow graph.

## Also

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