# Bilibili Creator Scraper (`romy/bilibili-creator-scraper`) Actor

Full Bilibili (哔哩哔哩) creator profile in one call: detail, uploaded videos, posts, favorite folders, live status, and follow counts. No login, cookie, or API key required.

- **URL**: https://apify.com/romy/bilibili-creator-scraper.md
- **Developed by:** [Romy](https://apify.com/romy) (community)
- **Categories:** Social media, Videos
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.24 / 1,000 creator records

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 Creator Scraper

Full Bilibili (哔哩哔哩) creator profile in **one call per creator**: detail,
uploaded videos, posts (dynamic tab), favorite folders, live status, and
follow counts. No login, cookie, or API key required.

### Why

Spun off from the sibling actor `bilibili-all-in-one-api` (same account) —
this reuses its already-verified request logic (the `x/v2/space` APP-sign
scheme, WBI-signed endpoints, etc.) rather than re-deriving it, but is
shaped as a classic input-driven batch actor instead of an always-on REST
API, matching how buyers in this Store category actually work: give a list
of creators, get a dataset back.

Most competing "Bilibili creator/profile" scrapers cover only one slice
(just uploads, or just profile info). This actor's differentiator is
aggregating **profile + uploads + posts + favorites + live status + follow
counts in one dataset row per creator** — everything the space page shows,
in one call.

### Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `creators` | string\[] | — (required) | Numeric mids or `space.bilibili.com/...` URLs |
| `includeVideos` | boolean | `true` | Fetch the uploaded-video list |
| `maxVideos` | integer | `50` | Cap on videos fetched per creator |
| `includePosts` | boolean | `true` | Fetch the dynamic/"Posts" tab (only the first batch is reliably reachable — see below) |
| `includeFavorites` | boolean | `false` | Fetch public favorite folders + their contents (1 extra call per folder, off by default since it's the priciest option) |
| `includeLiveStatus` | boolean | `true` | Fetch whether the creator currently has an active live room |

### Output

One dataset row per creator:

```json
{
  "mid": "3546723924314441",
  "profile": { "card": { "name": "...", "sign": "...", "fans": 29053, "vip": {...}, "official_verify": {...} }, "archive": {...}, ... },
  "videos": { "count": 86, "item": [ { "title": "...", "bvid": "...", ... } ] },
  "posts": { "list": [ ... ] },
  "favorites": null,
  "liveStatus": { "roomStatus": 0, "liveStatus": 0, ... },
  "relations": { "follower": 29053, "following": 3 }
}
```

Any section that errors or is disabled comes back as `null` rather than
failing the whole row — a creator with no live room, no posts, or no public
favorites is a real, valid result.

### Known limitations

- `posts` only returns the first batch. Confirmed live (in the parent
  `bilibili-all-in-one-api` actor's research): the response's
  `history_offset` cursor is intermittently blank, and feeding a real one
  back either returns empty or silently repeats the same first batch —
  never genuinely different content. Not a missing feature, a real
  upstream ceiling for an anonymous caller.
- Follower/following **lists** aren't available (only the counts, in
  `relations`) — the list endpoints are gated behind a real logged-in
  session on Bilibili's side, confirmed both on the web WBI path
  (risk-control blocked) and the APP-sign path (returns a "hollow success"
  with an empty list even for accounts with a nonzero count).

### Pricing

Pay-Per-Event, tiered (FREE/BRONZE/SILVER/GOLD/PLATINUM/DIAMOND =
100/92/85/78/72/68%, this account's standard ladder):

| Event | FREE price | Why |
|---|---|---|
| `creator-record` | $0.008 | One full aggregated creator record (profile + uploads + posts + favorites + live + relations) — priced above the ~$0.001-0.003/record competitors charge for a single data slice, reflecting the multi-section aggregation |

### Getting started

```bash
apify run
```

# Actor input Schema

## `creators` (type: `array`):

Bilibili creator mids (numeric) or space.bilibili.com profile URLs, one per entry.

## `includeVideos` (type: `boolean`):

Fetch the creator's uploaded-video list.

## `maxVideos` (type: `integer`):

Cap on how many uploaded videos to fetch per creator (paginated internally).

## `includePosts` (type: `boolean`):

Fetch the creator's dynamic/short-form posts.

## `includeFavorites` (type: `boolean`):

Fetch the creator's public favorite folders and their contents (one extra call per folder).

## `includeLiveStatus` (type: `boolean`):

Fetch whether the creator currently has an active live room.

## Actor input object example

```json
{
  "creators": [
    "3546723924314441"
  ],
  "includeVideos": true,
  "maxVideos": 50,
  "includePosts": true,
  "includeFavorites": false,
  "includeLiveStatus": true
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# 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 = {
    "creators": [
        "3546723924314441"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/bilibili-creator-scraper").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 = { "creators": ["3546723924314441"] }

# Run the Actor and wait for it to finish
run = client.actor("romy/bilibili-creator-scraper").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 '{
  "creators": [
    "3546723924314441"
  ]
}' |
apify call romy/bilibili-creator-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/bilibili-creator-scraper"
        }
    }
}
```

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/OYmca2pK9bI5dAgQG/builds/rbqPqgsakmp21W06C/openapi.json