Bilibili On-screen video comments API

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Bilibili On-screen video comments endpoint (bilibili/danmaku).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to bilibili and action to danmaku, and put the parameters inside params.
- Required parameters:
  - url: Specifies a full Bilibili video URL, formatted as https://www.bilibili.com/video/<BVID>. The url parameter fetches video comments on comments, first-part timed comments on danmaku, and audio transcription on subtitles, t…
- Optional parameters:
  - limit: The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows.
- Returns a list of records. Main fields of each record: id, text, video_id, video_time, video_time_seconds, mode, color, pool, sent_at.
- Example request body:
{
  "platform": "bilibili",
  "action": "danmaku",
  "params": {
    "url": "https://www.bilibili.com/video/BV1DYjA6KEJ7"
  }
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Code samples

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "bilibili",
  "action": "danmaku",
  "params": {
    "url": "https://www.bilibili.com/video/BV1DYjA6KEJ7"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

{
  "id": "req_…",
  "platform": "bilibili",
  "action": "danmaku",
  "results": [
    {
      "video_id": "BV1DYjA6KEJ7",
      "platform": "bilibili"
    }
  ],
  "count": 1,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

FAQ

Errors and billing

401

Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.

422

Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.

402

Insufficient balance. Top up first.

429

The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.

503

Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.

200 empty

The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

• Bilibili: Official Announcement on Upgrading AV Numbers to BV Identifiers ↗

  Bilibili's 2020 announcement defines BV identifiers as video submission IDs containing numbers and case-sensitive letters, distinguishing them from pure numeric AV numbers. This reference only explains video identifier types; this API accepts links per the format above and does not guarantee parsing for all legacy links or multi-part video segments.

  Checked 2026-09-04