Bluesky People search API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Search Bluesky for accounts matching a name or term, returning handle, display name, bio, avatar and verification flag. It matches profiles rather than post text, and a match does not confirm who a person is.

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

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Bluesky People search endpoint (bluesky/search_people).

Endpoint contract:
- 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 search_people, and put the parameters inside params.
- Required parameters:
  - keyword: Specifies user or account search terms for the search_people action. This endpoint returns matching user profile results and does not search post text; use user_posts with a complete handle to retrieve posts.
- Optional parameters:
  - limit: The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- 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": "search_people",
  "params": {
    "keyword": "coffee"
  }
}
- 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	`search_people`	Capability identifier, fixed value.
`keyword`	body.params	Not declared	Yes	-	Specifies user or account search terms for the search_people action. This endpoint returns matching user profile results and does not search post text; use user_posts with a complete handle to retrieve posts.
`limit`	body.params	`integer (1–200)`	No	`20`	The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

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": "bluesky",
  "action": "search_people",
  "params": {
    "keyword": "coffee"
  }
}'

[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; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.

json

{
  "id": "req_…",
  "platform": "bluesky",
  "action": "search_people",
  "results": [
    {
      "user_id": "（已隐去）",
      "username": "（已隐去）",
      "display_name": "（已隐去）",
      "bio": "（已隐去）",
      "url": "https://bsky.app/（已隐去）",
      "avatar_url": "https://cdn.bsky.app/（已隐去）",
      "is_verified": false,
      "joined_at": "2023-07-24T18:05:11.575000+00:00",
      "platform": "bluesky"
    },
    {
      "user_id": "（已隐去）",
      "username": "（已隐去）",
      "display_name": "（已隐去）",
      "bio": "（已隐去）",
      "url": "https://bsky.app/（已隐去）",
      "avatar_url": "https://cdn.bsky.app/（已隐去）",
      "is_verified": false,
      "joined_at": "2023-06-23T03:19:22.352000+00:00",
      "platform": "bluesky"
    }
  ],
  "count": 20,
  "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. 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: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
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).