DataNavoAPI / ANSWERS / BILIBILI

What should I check after a Bilibili API error -3?

What should I check after a Bilibili API error -3? Follow concrete contracts, examples and reviewable steps using Bilibili.

LOCAL SIMULATIONAll displayed records are fictional fixtures. Live APIs, payments and external email are disabled.中文版 ↗
01

Answer

Start by inspecting the contracts and local samples for Bilibili user profile, Bilibili video detail. Establish the input for bilibili.users.get, then check whether its account object contains the fields your task needs.

Record the HTTP status, error code, request ID and time. Third-party codes do not automatically share DataNavoAPI semantics; the local failure scenario tests recovery without reproducing platform restrictions. Do not loop retries or substitute browser cookies for a customer API key.

02

Relevant contracts

CapabilityObjectShapePagination
bilibili.users.getAccountitemNo cursor
bilibili.videos.getPostitemNo cursor
03

Input contract

Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.

  • Only send fields defined for this method; unknown fields are rejected before execution.
MethodFieldTypeRequirementMeaningEnum or boundExample
GETidstringRequiredUser number (mid), a string of digits: the number after space.bilibili.com/ in a space link—"8047632"
GETviewstringOptional / conditionalHow much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`).["compact","standard","full"]—
GETfieldsarrayOptional / conditionalReturn only these fields of each item, by path (`author.name`).maxItems: 64—
04

Complete one verification

Run one local fixture for a listed capability and inspect the object structure. Then filter, classify or export according to the question. A local sample cannot replace evidence for a real-platform conclusion.

json
{
  "capability": "bilibili.users.get",
  "method": "GET",
  "params": {
    "id": "8047632"
  }
}
TRY THE CONTRACT

Clear inputs. Inspectable output.

Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.

Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.

Download contract example (no execution) ↗

For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗