Bluesky Following API
API health
- 24h health
- Normal
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
See which accounts a Bluesky user follows, with each account's ID, handle, display name, bio and verification flag. Follow ties change over time and imply no affinity, contact or permission to message.
Send POST https://api.everyinfra.com/api/v1/social with platform set to bluesky and action set to following. Price $1.39 per 1,000 requests ($0.001389 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 Bluesky Following endpoint (bluesky/following).
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 bluesky and action to following, and put the parameters inside params.
- Required parameters:
- username: 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.
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 30)
- Returns a list of records. Main fields of each record: user_id, username, display_name, bio, url, avatar_url, is_verified, joined_at, source_username.
- Example request body:
{
"platform": "bluesky",
"action": "following",
"params": {
"username": "bsky.app"
}
}
- Price: $1.39 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 | bluesky | Platform identifier, fixed value. |
action | body | string | Yes | following | Capability identifier, fixed value. |
username | body.params | string | Yes | - | 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. |
limit | body.params | integer (1–100) | No | 30 | The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
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": "bluesky",
"action": "following",
"params": {
"username": "bsky.app"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
#{ "id": "req_…", "platform": "bluesky", "action": "following", "results": [ { "user_id": "•••", "username": "•••", "display_name": "•••", "bio": "•••", "url": "https://bsky.app/•••", "avatar_url": "https://cdn.bsky.app/•••", "is_verified": true, "joined_at": "2024-11-07T17:42:28.091000+00:00", "source_username": "bsky.app", "platform": "bluesky" }, { "user_id": "•••", "username": "•••", "display_name": "•••", "bio": "•••", "url": "https://bsky.app/•••", "avatar_url": "https://cdn.bsky.app/•••", "is_verified": true, "joined_at": "2024-11-21T21:11:36.371000+00:00", "source_username": "bsky.app", "platform": "bluesky" } ], "count": 15, "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 |
|---|---|
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 | Keeps the platform's own meaning |
source_username | 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.
Official references
#Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- AT Protocol: Handles and DIDs ↗
In the protocol, a handle is a domain-name style user identifier that resolves to a stable DID; the two are not interchangeable inputs.
Checked 2026-09-04