Bilibili Comments & Replies Scraper

Extract public comments and nested replies from known Bilibili videos. Provide BVIDs or video URLs and get structured rows for social listening, creator research, brand monitoring, market research, and AI dataset preparation.

Quick start

Start with one public video and a small comment limit:

{
  "bvidsOrUrls": ["BV1xx411c7mD"],
  "maxCommentsPerVideo": 10,
  "includeReplies": false,
  "proxyConfiguration": { "useApifyProxy": false }
}

Run the Actor, then open its dataset to export available rows as JSON, CSV, or Excel. This Actor does not discover videos or access login-only content.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

Bilibili comment threads contain buyer opinions, fandom reactions, creator feedback, and community signals. This Actor turns public comment and reply text into exportable rows with stable IDs and parent-child links.

• Public top-level Bilibili video comments and optional nested replies.
• Comment text, timestamps, likes, and public commenter fields.
• Parent-child relationships through rpid, rootRpid, and parentRpid.
• Optional anonymization of public commenter fields while retaining a stable hash.
• Available video titles and creator names. Comment rows are retained when this optional information is unavailable.

Who is it for?

• Social listening teams: review audience reactions under campaign or brand videos.
• Creator researchers: study engagement, recurring topics, and reply chains.
• Market researchers: export Chinese video-platform discussions for qualitative analysis.
• AI dataset builders: prepare public CJK/emoji-rich conversation text with timestamps and IDs.

Input settings

Setting	API key	Description
Videos	bvidsOrUrls	Public Bilibili BVIDs or video URLs to process.
Comment limit	maxCommentsPerVideo	Maximum top-level comments to save per video.
Include replies	includeReplies	Whether to collect nested replies.
Reply limit	maxRepliesPerComment	Maximum replies per top-level comment.
Order	sort	hot or time.
Anonymize users	anonymizeUsers	Removes member ID, name, and avatar URL while keeping memberHash.
Request delay	requestDelayMillis	Delay between requests.
Request retries	maxRequestRetries	Retries for temporary request failures.
Proxy	proxyConfiguration	Optional Apify proxy settings. Direct access is the default.

For a small discussion sample with replies:

{
  "bvidsOrUrls": ["BV1xx411c7mD"],
  "maxCommentsPerVideo": 25,
  "includeReplies": true,
  "maxRepliesPerComment": 2,
  "sort": "hot",
  "anonymizeUsers": true,
  "proxyConfiguration": { "useApifyProxy": false }
}

For top-level comments only, set includeReplies to false. Choose time to collect newest-first comments rather than the hot ordering.

Output data

Each dataset item is a public comment or reply row.

Fields	Description
sourceUrl, bvid, aid	Source input and resolved video identifiers.
videoTitle, videoOwnerName	Available video title and creator name, otherwise null.
commentType, isReply	Distinguish top-level comments from replies.
rpid, rootRpid, parentRpid	Stable comment/reply IDs and parent-child linkage.
message, createdAt, likeCount, replyCount	Comment text, time, and engagement.
memberMid, memberName, memberLevel, memberAvatarUrl, memberHash	Public commenter fields and stable hash.
sort, repliesTruncated	Collection order and reply-limit context.
apiCode, apiMessage, scrapedAt	Response context and collection timestamp.

Illustrative shape only. These values are not an observed extraction result:

{
  "sourceUrl": "BV1xx411c7mD",
  "bvid": "BV1xx411c7mD",
  "aid": 2,
  "videoTitle": "Example Bilibili video",
  "commentType": "reply",
  "rpid": "1234567890",
  "rootRpid": "1234567000",
  "parentRpid": "1234567000",
  "message": "Public comment text",
  "createdAt": "2026-07-18T08:00:00.000Z",
  "likeCount": 12,
  "memberHash": "a1b2c3d4e5f6a7b8",
  "isReply": true,
  "scrapedAt": "2026-07-18T08:01:00.000Z"
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing. A Start event (start) is charged once per accepted run.

A Comment or reply row event (item) is charged for each saved comment or reply. No per-row event is charged without a saved comment or reply.

Input without any valid BVID is rejected before the start event. An accepted run can incur the start charge even when it saves no rows.

See the live Pricing tab for current rates and discounts.

Tips for best results

• Start with one video. Use a small comment limit to check the discussion before collecting a larger sample.
• Bound reply collection. Replies add saved rows. Both limits apply per video or comment, not to the whole run.
• Keep the IDs when exporting. Use the parent-child fields to reconstruct conversations in your analysis.
• Review text before sharing. Anonymizing commenter fields does not remove personal information embedded in messages.

Limits and caveats

• Only public Bilibili video comments and replies are supported, not private, logged-in, paid, or restricted content. The Actor is not affiliated with Bilibili.
• Results depend on public availability and Bilibili's responses. Complete collection is not guaranteed, and optional video metadata can be missing.
• Explicitly empty comment threads can finish with zero rows. Temporary blocks or request failures do not prove that a video is private or deleted.
• Mixed batches can retain rows from successful videos when another video fails. Inspect the run summary for incomplete collection. If the processing window ends with unfinished work, the run fails while retaining saved rows and a checkpoint.
• anonymizeUsers removes the public member ID, name, and avatar URL, but keeps memberHash. Comment text and other remaining fields still need review before sharing.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~bilibili-comments-replies-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"bvidsOrUrls":["BV1xx411c7mD"],"maxCommentsPerVideo":10,"includeReplies":false}'

# Check the returned run ID until its status is SUCCEEDED.
curl 'https://api.apify.com/v2/actor-runs/RUN_ID' \
  -H "Authorization: Bearer $APIFY_TOKEN"

# Replace DATASET_ID with that run's defaultDatasetId to download its rows.
curl 'https://api.apify.com/v2/datasets/DATASET_ID/items?format=json&clean=true' \
  -H "Authorization: Bearer $APIFY_TOKEN"

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/bilibili-comments-replies-scraper').call({
  bvidsOrUrls: ['BV1xx411c7mD'],
  maxCommentsPerVideo: 10,
  includeReplies: false,
});
for await (const item of client.dataset(run.defaultDatasetId).iterateItems()) {
  console.log(item);
}

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/bilibili-comments-replies-scraper').call(run_input={
    'bvidsOrUrls': ['BV1xx411c7mD'],
    'maxCommentsPerVideo': 10,
    'includeReplies': False,
})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

MCP and AI agents

You can ask your AI assistant to collect data with Bilibili Comments & Replies Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Bilibili Comments & Replies Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/bilibili-comments-replies-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Bilibili Comments & Replies Scraper by Fetch Cat, or give it the identifier fetch_cat/bilibili-comments-replies-scraper.

Your assistant should inspect the input schema before running and read results from the returned run's dataset. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• "Collect 20 public comments from this Bilibili video and summarize recurring audience reactions."
• "Get comments from these two Bilibili videos with commenter names removed, then prepare a comparison of the main discussion themes."
• "Collect ten comments and up to one reply per comment from this video, then organize the returned conversation rows into a spreadsheet."

Normal Apify charges apply. Check the live Pricing tab before authorizing a run or asking your assistant to run a larger batch. Review comment text before sending it to an external assistant, even with anonymization enabled.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection. This Actor uses limited permissions, as required for prepaid-token access.

Some MCP setups also support paying for each request directly. That is a different payment option with separate eligibility rules. This Actor is not a Standby service, so use the prepaid-token flow rather than assuming direct per-request MCP payment is available.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does it scrape private or logged-in content? No. Only public video comments and replies are supported.

Can it discover videos by keyword? No. Use the related video search Actor first, then pass selected BVIDs here.

Why are there zero rows for a video? An explicitly empty thread may have no available comments. An unavailable video or disabled comments can also prevent collection. Check the run summary rather than treating zero rows as proof that no discussion exists.

Can I run it through an API or AI assistant? Yes. Use the API examples or connect through Apify's hosted MCP server above.

What affects the charge? Each accepted run has a start charge, with an additional event per saved comment or reply. See Pricing above and start with a bounded sample.

Related Actors

• Bilibili Video Search Scraper — discover Bilibili videos before collecting comments.
• YouTube Comments Scraper — collect discussions from YouTube videos.
• TikTok Comments Scraper — collect TikTok audience comments.
• Instagram Comments Scraper — collect public Instagram comment threads.
• YouTube Channel Videos Scraper — find channel videos for a separate YouTube research workflow.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥