You enjoyed one woodworking lesson and want to start at the beginning. The creator's profile mixes daily updates and several projects, so another title search will not necessarily reveal the intended sequence.
Identify the creator before collecting work
Use the bound category search with a documented search_type to find candidates, then verify the homepage and uid. Retrieve the profile and user-video list only after confirming the account. Matching titles from different creators do not establish one series.
Preserve the pages you actually retrieved
Use documented pn and ps settings, with keyword when narrowing within the account. Save request conditions and deduplicate video identifiers across pages. A total count is not your retrieved count. If you reviewed only recent pages, state that coverage in the index.
Confirm the sequence from the content
Inspect details or the original video for episode numbers, prerequisites and the creator's stated order. Your columns can include source, series name, stated episode, prerequisite and viewing status. Put unconfirmed relationships among standalone references rather than inventing a missing lesson.
Keep your progress during updates
Add first-seen entries on a later lookup without overwriting practice notes for existing videos. A missing result in one batch does not justify deleting the reference. AI can help categorize supplied notes but should not invent a curriculum. The finished index explains what to watch next and why; it is not evidence that videos have been downloaded or a subscription has been created.
Requests used in this project
- search by type：https://api.trmesh.com/openapi/api/v1/bilibili/app/fetch_search_by_type · Documentation
- Get information of specified user：https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_user_profile · Documentation
- Get user homepage video data V2：https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_user_post_videos_v2 · 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/app/fetch_search_by_type
| Parameter | Type | Required | Meaning |
|---|---|---|---|
keyword |
string | Yes | Search keyword |
search_type |
string | No | Search type (video/bangumi/pgc/live/article/user) |
cursor |
string | No | Pagination cursor, leave empty for the first page; for the next page pass back data.pagination.next from the previous response |
page_size |
integer | No | Page size |
order |
integer | No | Sort order (0=relevance, 1=newest, 2=views, 3=bullet comments) |
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/app/fetch_search_by_type"
params = {
"keyword": "原神"
}
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.
