Weibo User Videos Scraper

The Actor collects the videos one Weibo account has posted, one row per video, walking the feed until it runs out.

{
  "uid": "https://weibo.com/u/1749127163",
  "maxItems": 100
}

Accepted input

uid is required and takes either the account's numeric user ID or a link to the profile — weibo.com/u/<uid> and m.weibo.cn/u/<uid> have the ID pulled out of them for you. maxItems defaults to 100 and bounds the number of videos saved; 0 disables the bound.

Result fields

Every row carries the video exactly as Weibo returns it, passed through whole rather than narrowed down to a list somebody chose once. uid is added on top, so several accounts exported together stay separable and join back to profile rows. count is how many rows the page that row arrived on carried — a page size, not a total. Nothing in the response says how many videos the account has in all; the only way to know is to reach the end of the walk.

Where the walk stops

This is the one Weibo surface in this family that paginates by cursor, so it is the one that keeps going past a first page on its own.

The walk stops on the first page that comes back empty. A cursor that stops moving is the backstop, for a feed that re-serves the same page instead of ending. It deliberately does not stop on a has_more flag: on the sibling TikTok feed that flag stayed true through three consecutive empty pages with the cursor climbing 30, 60, 90, 120, so a run that trusted it would never stop — it would page until the platform timed it out, charging you for the compute the whole way.

If the run is interrupted, it resumes at the exact row it stopped on rather than re-walking the feed and pushing rows you have already paid for.

Fetching one video rather than a feed

There is no separate video record on Weibo. A video is a post that happens to have a video on it, so a single video is fetched with the Weibo Post Scraper, which returns is_video, the stream URLs and the duration on the post itself.

Empty is an answer, and a failure is a failure

An account that has posted no video, and a user ID nobody holds, both come back empty. The run succeeds, no rows are saved, and nothing is charged.

A run that could not reach the backend fails loudly instead, and so does a response in a shape this Actor does not recognise. An empty dataset always means "there were no videos" — it never stands in for a request that went wrong.

Related Actors

For the account behind the feed, use the Weibo Profile Scraper. For a single video or post, use the Weibo Post Scraper. For all of these behind one mode selector, use the All-in-One Weibo Scraper.