Weibo Account search API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Find Weibo accounts by nickname or keyword. Each account has UID, display name, bio, follower and following counts, verification flag and verification note. Up to 20 per page and the count varies; the first page often holds only the one or two closest matches. The UID works in profile and user_posts.

Price $0.81 per 1,000 requests ($0.000806 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 Weibo Account search endpoint (weibo/user_search).

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 weibo and action to user_search, and put the parameters inside params.
- Required parameters:
- keyword: A nickname or keyword to find Weibo accounts, such as People's Daily; each returned user_id works in profile and user_posts.
- Optional parameters:
- page_token: Page token. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received. Page sizes vary, and the first page often holds only the one or two closest matches.
- Returns a list of records. Main fields of each record: user_id, display_name, url, bio, follower_count, following_count, is_verified, verified_reason (Verification description of the account…), avatar_url, next_page_token (Page token (user_search, user_posts, to…).
- Example request body:
{
"platform": "weibo",
"action": "user_search",
"params": {
"keyword": "科技"
}
}
- Price: $0.81 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	`weibo`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`user_search`	Capability identifier, fixed value.
`keyword`	body.params	`string`	Yes	-	A nickname or keyword to find Weibo accounts, such as `People's Daily`; each returned `user_id` works in `profile` and `user_posts`.
`page_token`	body.params	`string`	No	-	Page token. Leave it out for the first page, then pass back the previous response's `next_page_token` exactly as received. Page sizes vary, and the first page often holds only the one or two closest matches; each page is one call, and the last page has no `next_page_token`.

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": "weibo",
  "action": "user_search",
  "params": {
    "keyword": "科技"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.

json

{
  "id": "req_…",
  "platform": "weibo",
  "action": "user_search",
  "results": [
    {
      "user_id": …,
      "display_name": …,
      "url": …,
      "bio": …,
      "follower_count": …,
      "following_count": …,
      "is_verified": …,
      "verified_reason": …,
      "avatar_url": …,
      "next_page_token": …,
      "platform": …
    }
  ],
  "next_page_token": …,
  "pagination": { … },
  "count": …,
  "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.
`display_name`	Display name; can differ from username.
`url`	Link to the record on the platform.
`bio`	Profile bio written by the account; may contain line breaks and emoji.
`follower_count`	Followers. null means not disclosed, not 0.
`following_count`	Accounts followed. null means not disclosed, not 0.
`is_verified`	Whether the platform verified the account. null means it cannot be determined.
`verified_reason`	Verification description of the account (user_search).
`avatar_url`	Avatar image link. Some platforms return sized CDN links that can expire.
`next_page_token`	Page token (user_search, user_posts, topic_search, user_post_search): pass it back unchanged as page_token for the next page. Every row of a page carries the same value, which also appears at the top level of the response; absent on the last page.
`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