Weibo Videos by user API
API health
- 24h health
- Normal
- Healthy / normal
- Available
Last 24 hours
Last 30 days
Page through the video posts of a Weibo account by numeric UID, newest first, about 20 per page, with play, like, comment and repost counts, duration, video URL and cover. 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_videos. 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 Videos by user endpoint (weibo/user_videos).
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_videos, and put the parameters inside params.
- Required parameters:
- user_id: Numeric Weibo UID, or a profile link containing /u/<UID>. Nicknames are not accepted; find the UID with user_search first.
- 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 posts.
- Returns a list of records. Main fields of each record: id, url, video_id (Video ID (video, collection_videos)), text, posted_at, play_count (Number of plays of a video (video, coll…), like_count, comment_count, repost_count, duration_sec (Video length in seconds (video posts on…), duration_seconds, video_url (Video link of the post); 18 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=weibo.
- Example request body:
{
"platform": "weibo",
"action": "user_videos",
"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_videos | Capability identifier, fixed value. |
user_id | body.params | string | Yes | - | Numeric Weibo UID, or a profile link containing /u/<UID>. Nicknames are not accepted; find the UID with user_search first. |
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 posts; 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_videos",
"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_videos", "results": [ { "id": "•••", "url": "https://m.weibo.cn/detail/5338700410258317", "video_id": "5338694882885678", "text": "小米18 Fold,新形态“中折叠”。这是小米交出的折叠屏新答案,兼具便携与视野的全新体验,优雅新生!\n\n合上,5.38″外屏,小巧精致,可以一手掌握;展开,7.58″内屏,纤薄舒展,一眼开阔。\n\n#小米18 Fold# 9月7日晚7点,正式发布。 http://t.cn/AX0qKSIo", "posted_at": "2026-09-02T06:00:29+00:00", "play_count": 352125, "like_count": 7928, "comment_count": 598, "repost_count": 146, "duration_sec": 29, "video_url": "https://f.video.weibocdn.com/o0/OvBmHtSTlx08AtTPzV0Q010412002UFx0E010.mp4?label=mp4_hd&template=640x368.25.0&ori=0&ps=1CwnkDw1GXwCQx&Expires=1795249428&ssig=RpfkWP3HLm&KID=unistore,video", "cover_image_url": "https://wx4.sinaimg.cn/orj480/001Un9Srly1igp9r77lc3j60hs0a874902.jpg", "hashtags": [ "小米18 Fold" ], "author_id": "1749127163", "author_name": "雷•••", "author_verified": true, "author_avatar_url": "https://tvax4.sinaimg.cn/•••", "platform": "weibo", "duration_seconds": 29 }, { "id": "•••", "url": "https://m.weibo.cn/detail/5338655200907501", "video_id": "5338647281729592", "text": "小米澎程N90 Max的新配色,酒红。\n\n灵感来源于陈年佳酿,值得细细品味。整体采用低明度、中高饱和度设计。光线较暗时,呈现深邃沉稳的酒红色泽;阳光照射下,透出宝石般浓郁而通透的光泽。 http://t.cn/AX0GkqJL", "posted_at": "2026-09-02T03:00:50+00:00", "play_count": 304573, "like_count": 3424, "comment_count": 304, "repost_count": 97, "duration_sec": 6, "video_url": "https://f.video.weibocdn.com/o0/wIYDUxADlx08AtGPIg7u010412000ENi0E010.mp4?label=mp4_hd&template=640x288.25.0&ori=0&ps=1CwnkDw1GXwCQx&Expires=1795249428&ssig=cuuw%2By5SfP&KID=unistore,video", "cover_image_url": "https://wx3.sinaimg.cn/orj480/001Un9Srly1igp4adyaqlj60hs080t8x02.jpg", "author_id": "1749127163", "author_name": "雷•••", "author_verified": true, "author_avatar_url": "https://tvax4.sinaimg.cn/•••", "platform": "weibo", "duration_seconds": 6 } ], "next_page_token": …, "pagination": { … }, "count": 5, "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. |
url | Link to the record on the platform. |
video_id | Video ID (video, collection_videos). |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
play_count | Number of plays of a video (video, collection_videos). Exact on collection_videos, and on video when you look the post up by post link or ID; approximate on video when you use a video link or 1034: ID, because Weibo shows a rounded figure. Not the same as view_count, the read count of a post. |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
comment_count | Comments. null means not disclosed, not 0. |
repost_count | Reposts (as distinct from quote posts). null means not disclosed. |
duration_sec | Video length in seconds (video posts on post_detail / user_posts, and video / collection_videos). |
duration_seconds | Duration in seconds. null for content that is not video or audio. |
video_url | Video link of the post. |
cover_image_url | Keeps the platform's own meaning |
hashtags | Hashtags in the text, in order of appearance; absent when there are none. |
author_id | Author's unique ID on the platform. |
author_name | Author's display name. |
author_verified | Whether the author carries Weibo verification (the V badge). Not returned on some requests (search). |
author_avatar_url | Author avatar URL. Not returned on some requests (search). |
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.