A friend recommends a short drama, but Bilibili results include summaries, edits and criticism that seem to describe different stories. Establish what each video is doing before using it to guide your viewing decision.
Confirm the production behind the title
Search the full title and verify characters or production context manually. Similar names and different versions should not merge into one set. Preserve search terms, date and filters. Use aid for details while relying on the returned material and original video to identify the work.
Label the kind of reference
Separate plot explanation, personal review and edited excerpts. An edit may omit context, and a narrator may mix interpretation into a summary. Note the covered story range and spoilers after reviewing the material. The endpoint does not validate the plot or guarantee a complete transcript.
Keep disagreements tied to examples
A card can contain source, subject, opinion, cited scene and what still needs checking in the drama. If someone calls a twist abrupt, identify the scene behind that judgment. AI-assisted notes should distinguish plot claims from opinions and avoid inventing motivations or endings.
Finish with a useful viewing entry point
Keep a short spoiler-conscious introduction, questions to watch for and any viewing-channel verification still required. Search results do not establish authorized distribution or provide a complete download. Repeated edits of one scene are not independent audience reviews. Watch a small section yourself before deciding whether to continue.
Requests used in this project
- Get general search data:https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_general_search · Documentation
- Get single video detail:https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_video_detail · Documentation
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_general_search
| Parameter | Type | Required | Meaning |
|---|---|---|---|
keyword |
string | Yes | Search keyword |
order |
string | Yes | Order method |
page |
integer | Yes | Page number |
page_size |
integer | Yes | Number per page |
duration |
integer | No | Duration filter |
pubtime_begin_s |
integer | No | Start date (10-digit timestamp) |
pubtime_end_s |
integer | No | End date (10-digit timestamp) |
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_general_search"
params = {
"keyword": "火影忍者",
"order": "totalrank",
"page": "1",
"page_size": "42"
}
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.