Comments under a headphone review repeatedly say they now have to buy it. Some readers appear enthusiastic; others are repeating a joke. A few emotional keywords cannot reliably establish what the audience thinks of the product.

Establish what the review actually claims

Inspect the video and relevant passages, noting the exact product model and claim. The bound detail lookup uses aid, while comment requests use bv_id. Prepare each identifier correctly. Comments about editing, the presenter or an introduction should not automatically become product evaluations.

Follow ambiguous remarks into their replies

Retrieve comments, then use bv_id and rpid for a reply lookup when meaning depends on context. Preserve parent-child relationships instead of classifying a short agreement on its own. The bound capabilities cover comments and replies, not danmaku collection, so restrict conclusions to the material actually available.

Use labels with an explanation

Possible labels include product experience, buying question, criticism of the test, entertainment and unclear. Record the reason for each interpretation, including any stated usage conditions. If AI assists, compare its labels with a small manually reviewed set. Check especially for sarcasm, copied jokes and quotations.

Finish with questions worth answering

A worksheet can contain source, subject of the remark, opinion type, contextual evidence and information to clarify. A sourced question about the noise-cancellation test environment is more useful than an unexplained overall sentiment score. Repeated jokes are not independent product experiences. The result can guide a clarification or follow-up demonstration, but the API does not determine reputation or predict purchase conversion.

Requests used in this project

Request URL and parameters

GET https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_video_comments

Parameter Type Required Meaning
bv_id string Yes Video id
pn integer No Page number

Run the Python example

Install requests and set TRMESH_API_TOKEN in your environment. Replace the sample identifiers with the public object you intend to inspect. Example IDs may no longer be available.

import os
import requests

# Read your own developer key from the server environment.
url = "https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_video_comments"
params = {
    "bv_id": "BV1M1421t7hT"
}
response = requests.get(
    url, params=params, timeout=30,
    headers={"Authorization": f"Bearer {os.environ['TRMESH_API_TOKEN']}"},
)
response.raise_for_status()
payload = response.json()
print(payload)  # Inspect the actual response before mapping fields

Endpoint documentation · Free profile tool

API calls use your TRMesh account allowance. Check the endpoint price before running a script.