# Bilibili Video Data API — Keyword & Creator Search (`nexgensignal/bilibili-video-data-api`) Actor

Search Bilibili by keyword for videos, or by creator/channel, with no login. Structured JSON: title, channel, play & danmaku counts. Optional sentiment + public social handles. Pay per result.

- **URL**: https://apify.com/nexgensignal/bilibili-video-data-api.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, Developer tools, Other
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 search results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Bilibili Video Data API — Keyword & Creator Search (No Login)

**Pay per result. Search Bilibili (B站) for videos by keyword — or, now, for creators/channels — and get clean, structured JSON back, with no login required.**

Hand this actor a keyword and get back one clean record per Bilibili video — title, channel, play count, danmaku count, category, duration, publish date, thumbnail, and a link — or switch to **creator mode** and get channels/UP creators matching your term instead. Optional add-ons score each result's sentiment and extract the public social links a creator published in their own description. No login, no cookies to manage — the actor handles Bilibili's public web-search signing for you.

### What this is, in one paragraph

Bilibili's search is one of the richest windows into Chinese-language video, but its public web API is protected by a request-signing scheme (the "wbi" signature) and a browser-fingerprint cookie, which is why a naive request just gets rejected. This actor does that handshake for you — it warms the required cookies, reads Bilibili's signing keys, and signs each search request correctly — then pages through the results and flattens each into a typed record. The upgrade over a keyword-only tool is a **creator/channel search mode**: the same clean interface, but pointed at Bilibili's UP-creator index, so you can discover channels, not just videos, for a term.

### Who buys this and for what job

- **Market and trend researchers** tracking what's popular on Bilibili for a topic, brand, or product.
- **Influencer and creator-discovery teams** finding channels in a niche via creator mode, ranked by fans.
- **Social and competitive analysts** measuring reach (play and danmaku counts) across a keyword's top videos.
- **Builders and agents** who need a keyless, structured Bilibili search feed without solving the signing themselves.

### The upgrade: creator/channel search

Set `searchType` to `creator` and the same actor searches Bilibili's UP-creator index instead of videos: each record is a channel — name, channel id, follower (fans) count, sign/description, a `space.bilibili.com` link, and avatar. Keep it on `video` (the default) for the classic keyword video search. One interface, two lenses on the platform.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `apify-actor-start` | $0.005 | $0.005 | $0.005 | $0.005 |
| `apify-default-dataset-item` | $0.05 | $0.045 | $0.04 | $0.0335 |
| `addon-sentiment-scored` | $0.02 | $0.02 | $0.02 | $0.02 |
| `addon-social-handles-extracted` | $0.10 | $0.10 | $0.10 | $0.10 |

A small start fee plus one item charge per result. The two optional add-ons bill per result only when you turn them on.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `keyword` | string | *(required)* | Search keyword. |
| `searchType` | string | `video` | `video` = keyword video search; `creator` = channel/UP-creator search (the upgrade). |
| `max_results` | integer | 30 | Maximum results delivered (1–1000). |
| `addonSentimentScored` | boolean | false | Add a sentiment score to each result. |
| `addonSocialHandlesExtracted` | boolean | false | Extract public social handles/links from each description (emails/phones excluded). |

### Output

One JSON object per result. Real example (video):

```json
{
  "record_id": "video:BV1abc",
  "result_type": "video",
  "bvid": "BV1abc",
  "title": "3小时超快速入门 Python — 动画教学【2026新版】",
  "author": "林粒粒呀",
  "author_id": "456",
  "category": "Tech",
  "duration": "3:12:04",
  "play_count": 7589855,
  "danmaku_count": 1200,
  "url": "https://www.bilibili.com/video/BV1abc",
  "sentiment": {"label": "positive", "score": 1.0},
  "observed_at": "2026-08-25T00:00:00Z"
}
```

A creator record carries the channel `author`, `author_id`, follower count (`favorites`), `description`, `video_count`, and a `space.bilibili.com` `url`. An unbilled `RUN_RECEIPT` records the keyword, search type, add-ons, and how many results were delivered.

### Field reference

Each record carries `record_id`, `result_type` (`video` / `creator`), `bvid`/`aid` (videos), `title`, `author` and `author_id` (the public channel), `description`, `category`, `duration`, `play_count`, `danmaku_count`, `favorites` (fans for creators), `video_count` (creators), `pubdate`, `thumbnail`, and `url`. With add-ons on: `sentiment` (label + score) and `social_handles` (public links, emails/phones excluded). Provenance travels on every record.

### How a run works

The actor first performs Bilibili's public web-search handshake: it warms the fingerprint cookie from the homepage and reads the current wbi signing keys, then signs each search request with the correct `w_rid`/`wts` parameters. It pages through the video or creator results up to your `max_results`, strips search-highlight markup from titles, and — as a privacy measure — scrubs any email- or phone-shaped strings out of free-text descriptions before delivery. If Bilibili rotates its anti-crawl keys mid-run, the actor refreshes them and retries. Each result is delivered and charged; the optional sentiment and social-handle add-ons bill per result only when enabled.

### Working with the data

The `record_id` is stable per video or channel, a clean de-duplication and join key. `play_count` and `danmaku_count` give a direct reach-and-engagement read across a keyword's top videos; in creator mode, `favorites` (fans) ranks channels. Turn on sentiment for a quick positive/negative read across a result set, and social handles to collect the public links a creator chose to publish — with emails and phone numbers stripped so no private contact data is compiled. Feed the output into a trend dashboard, an influencer shortlist, or an agent's research step.

### Honest limitations

- **Public search metadata.** Values are Bilibili's public web-search results at query time; counts move and search ranking changes.
- **No login, no private data.** No account is used; channel/author names are public platform identities on the videos, and emails/phones are scrubbed from descriptions — no private user data is collected or emitted.
- **Chinese-language platform.** Titles and descriptions are largely Chinese; the sentiment lexicon is bilingual but lightweight.

### The add-ons in depth

The two optional add-ons match the original tool's, billed per result only when switched on. **Sentiment scoring** runs a lightweight bilingual lexicon over each result's title and description and returns a `{label, score}` object — a fast positive/neutral/negative read you can aggregate across a keyword's results to gauge the tone of coverage. **Social-handle extraction** pulls the public social links and handles a creator chose to publish in their own description (Weibo, Douyin, X, YouTube, and bare URLs), while explicitly excluding anything email- or phone-shaped, so you collect the creator's public presence without compiling private contact data. Both are off by default, so a plain search never pays for them.

### Use with AI agents and schedules

Because the output is flat JSON keyed by a stable `record_id`, an agent can call this actor as a tool and reason over the results directly — "find the ten most-played Bilibili videos about my product this week, and score their sentiment" is a single call with `addonSentimentScored` on. In creator mode, an agent can build an influencer shortlist for a niche ranked by fans. Paired with a scheduler, a saved keyword becomes a standing trend monitor; because each run is bounded by `max_results` and priced per result, the cost stays small and predictable.

### Differentiation

A **Bilibili video-and-creator search API** with no login required — the actor solves Bilibili's public web-search signing for you — upgraded with a creator/channel search mode alongside keyword video search. Keyless, pay-per-result, callable from code or an AI agent.

***

*Source: Bilibili public web search (bilibili.com). Public video and creator-channel metadata as returned; reformatted to per-item records, linking back to the source. No login; no private user data (email/phone) collected or emitted.*

# Actor input Schema

## `keyword` (type: `string`):

Search keyword (video title/creator).

## `searchType` (type: `string`):

video = keyword video search; creator = channel/creator (UP) search (the upgrade).

## `max_results` (type: `integer`):

Maximum results delivered.

## `addonSentimentScored` (type: `boolean`):

Add a sentiment score to each result (billed per record).

## `addonSocialHandlesExtracted` (type: `boolean`):

Extract public social handles/links from each description, excluding emails/phones (billed per record).

## Actor input object example

```json
{
  "keyword": "游戏",
  "searchType": "video",
  "max_results": 30,
  "addonSentimentScored": false,
  "addonSocialHandlesExtracted": false
}
```

# Actor output Schema

## `results` (type: `string`):

Delivered records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keyword": "游戏",
    "searchType": "video",
    "max_results": 30
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/bilibili-video-data-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keyword": "游戏",
    "searchType": "video",
    "max_results": 30,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/bilibili-video-data-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keyword": "游戏",
  "searchType": "video",
  "max_results": 30
}' |
apify call nexgensignal/bilibili-video-data-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/bilibili-video-data-api"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/fRfvPFDHLKfxl6GHR/builds/2HGVD4D4H8BpNb06A/openapi.json