Bilibili Comments & Danmaku Scraper API, No Login – B站 哔哩哔哩
Pricing
Pay per event
Bilibili scraper API, no login: video comments, replies, danmaku (弹幕), search videos, video details, user profiles, creator videos, followings, popular & hot videos, weekly must-watch, precious, ranking, hot search (热搜), live rooms from B站/哔哩哔哩 as JSON. Lean AI-agent output, dry run. $0.005/video.
maxItemsPerInput/maxItems ask for more (up to 5,000 per keyword), the Actor sweeps publish-date windows newest first inside dateFrom/dateTo (a window that is itself capped is split down to 1 day before its pages are read; sparse windows widen up to 1 year). Same order and filters; duplicates are skipped free; the summary notes say how many windows/requests the sweep used. Locally 原神 1,300 videos: 1,300 distinct in 30 requests, 21 s (2.0.3 stopped at ~964–1,021 distinct).limits.searchDepth documents the sweep.GaETkx5obJTZbDFjO)keywordComments (aliases keyword_comments, comment_research): keyword → top maxVideos videos (sortBy, dateFrom/dateTo, minViews, durationFilter, expandQuery) → commentsPerItem comments (commentSort hot|newest) → replies (replyDepth 0|1, repliesPerComment) → free insights row per keyword. matchTerms keeps matching top-level comments/danmaku (filters after fetching). Without keywords but with urls it runs comments on them (routing bug in the unreleased v2 draft fixed: it ran videoDetails).isPartial, unavailableFields[], collectionWarnings[]; summary adds requested, perInput[] (returned per input, status), pagesFetched, isPartial.likesPer1kViews, commentsPer1kViews, engagementRate, danmakuPerMinute, detailLevel (formulas in capabilities.computedMetrics).deltaKey + trackMetrics: true → viewsDelta, likesDelta, commentsDelta, danmakuDelta, favoritesDelta, coinsDelta, sharesDelta, engagementRateDelta (creators: followersDelta, likesTotalDelta, videosCountDelta), snapshotAt, previousSnapshotAt, hoursSincePrevious.include: ["insights"], default on for keywordComments): top terms (CJK bigrams merged into trigrams when the trigram explains every use, e.g. 评论区 instead of 论区), emotes, matchTerms counts, most-liked comments, top videos, heuristic lexicon sentiment (no LLM), danmaku peak minute and a per-video danmaku profile (timelinePerMinute, peakMinute, poolFetched vs returned, uniqueSenders with include author).video-basic/video-enriched → result); the first event that exists in the live pricing is charged, so today every video row is still result ($0.005). No price or event changed.keywordComments with only urls now keeps its own defaults when it falls back to comments (commentsPerItem as the per-video limit, default 10; insights row on; replies on with 2 per comment). It returned 20 comments and no insights row in 2.0.1.maxVideos, commentsPerItem, replyDepth, repliesPerComment, commentSort, insights, trackMetrics, matchTerms. All v1.x inputs and the compact default output keep working (new fields are only added).exampleInput on each operation of the free capabilities row (same list, unit-tested against the input schema).include: details costs 1 batched request per 50 videos in compact/lean mode (was documented as 1 per video); the 512 MB hint for big full-mode runs states the measured 1.7–2.9× speed-up; README speed line uses platform numbers.iMHCt1JnAiW8EpLfH; limits removed where public, faster heavy runs; same prices and events; v1.2 inputs and default output unchanged)followings (关注列表): the accounts a creator follows, from Bilibili's public app endpoint (the web endpoint needs a login). User rows billed as profile, with new keys followingOf and followedAt. Bilibili shows logged-out visitors the newest 250 (5 pages × 50); creators who hide the list get a NO_RESULTS row that says so.trend.isCommercial works (was always null): the hotword list (same keywords, same order) is read in parallel and its commercial flag merged.include: details in compact/lean mode is batched: 1 request per 50 videos instead of one view call per video (field-identical on a 50-video check). Heavy compact run (300 videos + details/owner/topComments) 106 s → 69 s, −35 % CU, side by side (37.5 s in the release regression).ugc_season), which is part of the raw record; the summary now suggests 512 MB for big full runs (measured 72 s vs 105–212 s at 256 MB; CU 0.0100 vs 0.0077–0.0147).timingsMs.cpu (process CPU ms). Capabilities notAvailable lists the login-only data re-checked on 2026-10-13 (subtitles, fan lists, commenter IP region, danmaku history).ER1Q5MN9OBfIMLlA2)outputMode: "full" writes rows in batches of 25 (was 200) and runs at most 8 requests in parallel (was 16); 300 full rows with details+owner+topComments 187 s → 168 s, −10 % CU, −19 % peak memory vs 1.2.5 in a side-by-side run.outputMode: "lean" (opt-in): type + id + curated fields per row kind, null/empty/false omitted, envelope (operation, input, queryUsed, fetchedAt) once in the summary row, url derivable from id (patterns in the summary and capabilities), text cut to maxTextChars (default 300, truncated: true), dates YYYY-MM-DDTHH:MMZ UTC. Lean also skips enrichment requests its fields do not need (e.g. tags). Measured: −64 to −84 % tokens per row (median −77 %); table −71 to −90 % (median −83 %). leanFormat: "table" adds one TSV block per row kind (header once) to the summary row and key-value record LEAN_TABLE; rows are still pushed and billed the same. New input maxTextChars (any mode).config.media_id) and the issue's public media list (full stats), with the web endpoint as fallback.rankingCategory also accepts names (gaming, music, tech, …).precious (入站必刷, ~100 all-time must-watch videos, full stats).deltaKey monitoring mode (only rows not returned before; skipped rows free), allParts for danmaku of multi-part videos, danmakuSource: "segments" (XML pool + 6-minute protobuf segments, deduplicated: e.g. 2,943 vs 1,200 rows on one part), userVideos with sortBy: "views".categoryName was null on videoDetails/userVideos rows (Bilibili stopped sending tname) → v1 zone name table; categoryId is now the v1 zone id on every operation (videoDetails used tid_v2); creator uploads stopped at 100 with a NOT_FOUND row (page size 100 + cursor = -400) → page size 50 after the first page; articlesCount was always 0 (card) → creator navnum (only requested when the field is wanted); BGM pseudo-tags ("发现《…》") and duplicate tags removed; width/height swapped for rotated (portrait) uploads; isOriginal documented (copyright 3 = not declared → null).estimatedRows, estimatedSeconds, realistic caps for weekly/precious/ranking/danmaku. Summary nextSteps suggests lean mode on big compact runs.zKvLPo3k6Is1d0Gg8)Actor.pushData(rows, event)), in the background while the next page loads, instead of two API calls per row. Same per-row prices and chargedEventCounts.fields[] now also limits requests. Tags, ownerFollowers, topComments and view-only stats are fetched only when their field is requested (popular 50 with fields:["title","views"] = 1 request instead of 51). Search rows reuse their own tags with include: ["details"].pagelist call instead of the full video view; one shared WBI key fetch.requestDelayMs default 250 → 0; the Actor raises the delay to 250 ms and halves parallelism automatically after the first rate-limit / risk-control answer.apify/actor-node:22-slim base, npm ci, node started directly (no npm wrapper), V8 heap capped at 75 % of run memory. Peak memory ~70 MB → ~35–45 MB. Default run memory 512 → 256 MB (minMemoryMbytes 128).timingsMs (startup, first row, total).minViews / minLikes / dates / dedupe are checked on list data before any per-video request; rows that cannot be afforded under maxItems / maxCostUsd are not enriched.billedEvents / chargedUsd now read the SDK's charge counter (the batched charge result could be counted twice on the platform; the platform's chargedEventCounts was always right). Ranking fallback is now WBI-signed cookie-less (the guest-session call gets -352). Hard watchdog on every HTTP request (one platform run stalled with requests in flight). topComments fetch uses a 5-comment page.operation, default auto): search, videoDetails, comments, replies, danmaku, related, userProfile, userVideos, searchUsers, popular, weekly, ranking, hotSearch, liveRoom, plus free capabilities. New inputs users[] and ids[] (auto-routed by shape: BV…:commentId, mid:…, space/live links).include[] (tags, details, owner, parts, topComments, comments, replies, danmaku, author, liveRoom), fields[] projection, outputMode compact|full (full adds raw), filters before billing (dateFrom/dateTo incl. relative 7d, minViews, minLikes, sortBy, durationFilter, dedupe), limits (maxItemsPerInput, maxItems = run total, maxCostUsd), dryRun (free plan row with estimated cost).expandQuery, default on): shared curated dictionary work/actors/_shared/query_expansion/en_zh.json (~940 entries), copied to src/data/en_zh.json (npm run sync-dict); keywords ≤2 chars stay literal; Chinese searched first, original fills the shortfall; rows show queryUsed.type, operation, input, queryUsed, id, url, fetchedAt, rank; kinds video / comment / danmaku / user / trend / liveRoom; free error rows (errorCode, errorMessage, suggestedFix; new codes NOT_SUPPORTED, INTERNAL_ERROR), free summary row last (counts, billedEvents, chargedUsd, stopReason, warnings, nextSteps), plan, capabilities. Output field mode → operation, scrapedAt → fetchedAt (breaking for v0.x output consumers); bvid now canonical (derived from aid).comment $0.001, danmaku $0.0001, profile $0.003 (creator or live room), trend $0.001; result $0.005/video and apify-actor-start unchanged. Submitted 2026-10-12 22:58 IST via API; no paying users, so effective immediately (no 14-day notice needed)./x/v2/reply/wbi/main, 20/page, paginated – guest cookies cap comments at 3), replies (/x/v2/reply/reply), danmaku XML (/x/v1/dm/list.so), related, user card, medialist uploads (space arc search is 412/-352 for guests), user search, hot search (search/square, fallback hotword), live rooms; weekly now WBI-signed (unsigned gets -352); offline BV↔AV conversion.keywords: ["原神"]), dataset schema with all kinds (no required keys, nullable types) + views per kind, output schema results + runSummary. Store title/description/SEO rewritten; README "For AI agents" section.mode (wins over the injected operation: auto default), searchKeywords, videoUrls, searchOrder, searchDuration, fetchDetails, includeComments, includeTags, maxCommentsPerVideo, includeCommentAuthor, legacy per-keyword maxItems.mode auto – Bilibili: added auto, no longer required; explicit modes still work); misplaced inputs auto-corrected (site URL in keywords → fetched, plain word in urls → searched); explicit mode with missing input falls back to the given input.type: "error" dataset rows with errorCode / errorMessage / suggestedFix (never billed); input, not-found and no-result problems now end SUCCEEDED with these rows; status message lists codes + first fix; RUN_SUMMARY has errorRows, notes.type enum incl. error, Errors view; output schema descriptions updated.affectionate_greengage username in API/MCP examples./x/web-interface/ranking/v2; plain cookie-less request with rank-page referer tried first.keywords[] (was searchKeywords) and urls[] (was videoUrls); old names still accepted as aliases.mode is required with no default (MCP marks it REQUIRED); prefill examples for mode, keywords, urls, maxItems.maxItems 50 → 10; in search mode it now applies per keyword..actor/output_schema.json (videos dataset + RUN_SUMMARY record), required for Store publishing and shown to agents.videoDetails rank = position in the urls input.defaultMemoryMbytes + Actor defaultRunOptions).actor-start (charged only if configured; Apify's synthetic apify-actor-start also works) + result per video.actor-start + result per video, stops at the run's max charge.