Bilibili Scraper Pro (B站)
Pricing
from $3.00 / 1,000 videos
Go to Apify Store
Bilibili Scraper Pro (B站)
Pricing
from $3.00 / 1,000 videos
Search Bilibili videos by keyword (Chinese or English), e.g. 原神, AI, vlog.
Individual videos: https://www.bilibili.com/video/BV1..., BV1... or av123.
Scrape latest uploads of these creators. Numeric UID or https://space.bilibili.com/.
Output one profile row per creator: followers, following, likes, total views, level, bio, verification.
Scrape the 综合热门 (popular) board.
Ranking board by category id (rid). 0 = all-site ranking. Some category ids may not have boards; errors are reported in OUTPUT.
Scrape the latest weekly must-watch issue (best effort; Bilibili may rate-limit it).
Max videos per keyword / creator / board.
totalrank = relevance, click = most viewed, pubdate = newest, dm = most danmaku, stow = most favorited.
One extra request per video for coins, shares, multi-part (P) pages, subtitle availability, full description. Slower, more rate-limit prone. Popular/ranking already include full stats.
Embed related/recommended videos list (bvid, title, uploader, views).
Max related videos embedded per video.
Tries Bilibili's AI video summary (AI视频总结). In our tests it was NOT returned to anonymous requests, so expect aiSummary.available=false. Adds one request per video.
Scrape public comments. Anonymous limit: Bilibili returns ~3 top-level (hot) comments per video; the Actor then paginates their full reply threads. Expect tens to a few thousand comments per video depending on how many replies those top comments have — not the full comment section.
Includes replies.
Paginate replies under top-level comments (main way to get more than 3 comments).
none = no author fields (default, privacy-friendly); hashed = pseudonymous author id + level/region; public = public username & UID.
off; summary = one cheap row per video (top terms, per-minute density timeline, peak); raw = individual danmaku rows; both.
Raw rows are sampled evenly across the video timeline if there are more.
Included in the price. Requests go direct; only after Bilibili rate-limits (HTTP 412) the Actor switches to Apify datacenter proxy, then (within a small developer-set budget) residential proxy. Danmaku files never use residential.
Optional. If set, ALL requests use your own proxy (billed to your account per Apify rules) and the built-in fallback is disabled.
{ "useApifyProxy": false}Polite global delay; auto-increases when rate limited.