Weibo Following list API
API health
- 24h health
- Normal
- Healthy / normal
- Available
Last 24 hours
Last 30 days
List the accounts a Weibo user follows, by numeric UID, each with UID, name, bio, avatar, follower, following and post counts, verification and gender. Weibo shows logged-out visitors only the first page, about 20 accounts, so there is no next page.
Send POST https://api.everyinfra.com/api/v1/social with platform set to weibo and action set to following_list. Price $0.79 per 1,000 requests ($0.000792 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 Following list endpoint (weibo/following_list).
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 following_list, and put the parameters inside params.
- Required parameters:
- user_id: Numeric Weibo UID, or a profile link containing /u/<UID>. Anything else returns 422 and is not charged; nicknames are not accepted, so find the UID with user_search first.
- Optional parameters:
- limit: The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows.
- Returns a list of records. Main fields of each record: user_id, display_name, url, bio, avatar_url, follower_count, following_count, post_count, is_verified, verified_type, verified_reason (Verification description of the account…), gender; 13 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=weibo.
- Example request body:
{
"platform": "weibo",
"action": "following_list",
"params": {
"user_id": "1749127163"
}
}
- Price: $0.79 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 | following_list | Capability identifier, fixed value. |
user_id | body.params | string | Yes | - | Numeric Weibo UID, or a profile link containing /u/<UID>. Anything else returns 422 and is not charged; nicknames are not accepted, so find the UID with user_search first. Weibo shows logged-out visitors only the first page of the list, about 20 accounts, returned in one call; there is no paging and limit has no effect. |
limit | body.params | integer (1–) | No | - | The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows. |
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": "weibo",
"action": "following_list",
"params": {
"user_id": "1749127163"
}
}'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": "weibo", "action": "following_list", "results": [ { "user_id": …, "display_name": …, "url": …, "bio": …, "avatar_url": …, "follower_count": …, "following_count": …, "post_count": …, "is_verified": …, "verified_type": …, "verified_reason": …, "gender": …, "location": …, "platform": … } ], "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. |
avatar_url | Avatar image link. Some platforms return sized CDN links that can expire. |
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. |
is_verified | Whether the platform verified the account. null means it cannot be determined. |
verified_type | Keeps the platform's own meaning |
verified_reason | Verification description of the account (user_search). |
gender | Keeps the platform's own meaning |
location | Location description passed through as is; the format varies by platform. |
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.