Weibo User album API
API health
- 24h health
- Normal
- Healthy / normal
- Available
Last 24 hours
Last 30 days
Page through the photos in the Album tab of a Weibo account's profile, newest first, by numeric UID. Each row is one photo with image_url, post_id and post_url. Up to about 20 per page and often fewer; pass next_page_token back as page_token for more.
Send POST https://api.everyinfra.com/api/v1/social with platform set to weibo and action set to user_album. 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 User album endpoint (weibo/user_album).
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_album, and put the parameters inside params.
- Required parameters:
- user_id: Numeric UID of the Weibo account, or a profile link that contains /u/<UID>. Nicknames are not accepted; look them up first with user_search.
- 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, with the other parameters unchanged. Pages hold up to about 20 photos and are often shorter.
- Returns a list of records. Main fields of each record: id, image_url, post_id (Post ID), post_url.
- Example request body:
{
"platform": "weibo",
"action": "user_album",
"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 | user_album | Capability identifier, fixed value. |
user_id | body.params | string | Yes | - | Numeric UID of the Weibo account, or a profile link that contains /u/<UID>. Nicknames are not accepted; look them up first with user_search. |
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, with the other parameters unchanged. Pages hold up to about 20 photos and are often shorter; each page is one call and limit has no effect. Tokens last 24 hours, and the last page has no next_page_token. |
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": "user_album",
"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": "user_album", "results": [ { "id": …, "image_url": …, "post_id": …, "post_url": …, "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 |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
image_url | Image link. Capabilities with several images may return an image_urls array. |
post_id | Post ID. On comments, the post the comment belongs to; on user_album, the post the photo belongs to. |
post_url | 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.