> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# How do I resume Bilibili research after 412, -352 or a key-validation error?

> Reuse selected videos and saved comments, fill object-specific gaps, distinguish platform errors from authentication, and report supported findings.

**Keep the selected videos and the comments already read, identify the missing page or context, then fill only that gap with `bilibili.web.fetch_video_comments` or `bilibili.app.fetch_video_comments`.** An error from an old collector does not mean you have to discard the searches and analysis already completed. HTTP 412, `-352` and `-3` come from the original Bilibili request or client; a BeatAPI call needs only your BeatAPI API key, the BV ID and the page number.

For example, an editing-course review has several selected videos and some saved popular comments when reading stops. Keep the BV IDs, selection reasons, excerpts and open questions. Then decide whether the missing material is new comments, reply context or another relevant video.

## Identify what needs resuming

| Existing progress                          | Next step                                                          |
| ------------------------------------------ | ------------------------------------------------------------------ |
| Verified video list and readable originals | Continue explanation and question analysis                         |
| Verified BV identifier, comments unread    | Retrieve an initial comment batch                                  |
| Saved root comment needing context         | Confirm the root comment's identifier and read the replies         |
| Unusable old pagination state              | Preserve prior scope, begin a new observation and match overlap    |
| Creator mid or unresolved short code only  | Establish the video rather than substituting an account identifier |

See [BV/AV identity](/faq/bilibili-bv-comments). Cursors, signatures and cache fields from the old collector are not inputs for a BeatAPI action.

## How can you read comments for a verified BV?

Request the first Web comment page with `bilibili.web.fetch_video_comments`:

```json
{
  "action": "bilibili.web.fetch_video_comments",
  "params": {"bv_id": "<confirmed_bv_id>", "pn": 1}
}
```

Send the request to `POST https://api.beatapi.io/v1/social-data/call` with normal BeatAPI Bearer authentication. To choose newest or popular ordering explicitly, use `bilibili.app.fetch_video_comments` as described in the [ordering FAQ](/faq/bilibili-comment-order). Save the Web and App results separately, and do not pass an old ordering or cursor to a new action.

Save the video identity, action, actual inputs, time and request ID. The comment actions have no recorded fixed list or identifier paths, so check the actual returned objects before merging material, and do not reuse field names from the old collector.

## Where should you look when you see 412, -352 or -3?

Start with the service that returned the error. Record the HTTP status and response message separately so you or a teammate can trace the failure later.

| What you see                                                         | First step                                                                                 |
| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| HTTP 412 from the original direct Bilibili request                   | Save the status and mark that page as unread                                               |
| `-352` or a risk-control validation message in the original response | Save the message and identify the video or account you were reading                        |
| `-3` or a key-validation error in an older client                    | Check the client version and the maintainer's notes                                        |
| An authentication error on your BeatAPI call                         | Check that the request includes your BeatAPI API key in the `Authorization: Bearer` header |

`wbi`, `appkey` and `sign` belong to the original web or client request, not to BeatAPI. To continue with `bilibili.web.fetch_video_comments`, have your BeatAPI API key, the video's BV ID and the page number ready.

## How do you compare old and new material?

1. Link old and new material by confirmed video identity.
2. Match comments by their actual stable comment identifiers.
3. Keep every observation; do not overwrite the original text with a new value.
4. Record differences in version, collection time or ordering.

In the teaching table, list supported questions, missing conditions, unread material and failed reads separately. A sourced “missing menu” question can go to version review right away. A video that failed to read stays on the unfinished list; do not record the failed video as having no questions.

## What should the restored workflow deliver?

Hand off the supported course improvements with excerpts and sources, followed by the unfinished videos and replies and the next steps. Do not count repeated material as additional learners. For each additional read, record whether the read added a new condition or question.

For the assistant:

> Resume this Bilibili course review by reusing selected videos and saved comments. Fill specific material gaps rather than restarting all searches. Attach excerpts and sources to questions and improvements. Begin a separate observation where old pagination is unclear, reporting relationships to prior material and remaining work.

Budget only the missing reads with current [pricing](https://beatapi.io/pricing). Reclassifying or rereading saved material does not require a new request.