Weibo Featured video feed API
API health
- 24h health
- Normal
- Healthy / normal
- Available
Last 24 hours
Last 30 days
Read the Featured feed of Weibo's video home page, up to 9 videos per page, each with post ID, text, author name, publish time, play count, duration 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 video_feed. 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 Featured video feed endpoint (weibo/video_feed).
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 video_feed, and put the parameters inside params.
- No required parameters.
- 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. Up to 9 videos per page; each page is one call and limit has no effect.
- 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": "video_feed",
"params": {}
}
- 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 | video_feed | Capability identifier, fixed value. |
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. Up to 9 videos per page; each page is one call and limit has no effect. The feed is pushed fresh by Weibo and videos from earlier pages are not repeated, so some pages are not full; keep going while the response has a next_page_token. Tokens last 24 hours. |
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": "video_feed",
"params": {}
}'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": "video_feed", "results": [ { "id": …, "url": …, "video_id": …, "text": …, "posted_at": …, "play_count": …, "like_count": …, "comment_count": …, "repost_count": …, "duration_sec": …, "duration_seconds": …, "video_url": …, "cover_image_url": …, "hashtags": …, "author_id": …, "author_name": …, "author_verified": …, "author_avatar_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. |
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.