You are organizing your own published demonstrations and notice that one video contains several segments. A title and one link are not enough to identify which part a later process retrieves.
Locate the intended work in the account list
Retrieve posts by uid and preserve pagination conditions. Use details and the original page to verify the video and its parts. The bound detail endpoint uses aid, while playback information requires bv_id and cid. Do not transfer a numeric identifier into a BV parameter merely because both refer to video content.
Confirm the segment identifier
Check available details and the original page for the correct relationship between the video and cid. If the segment cannot be identified confidently, leave it pending rather than borrowing a value from another work. Retrieving one segment does not process every part of a multi-part video.
Separate media information from processing status
A register can contain account source, original link, BV identifier, segment identifier, lookup time and later processing state. Preserve what the response actually provides without assuming a particular address structure or permanent availability. An address is not a saved file, merged media or verified offline copy.
Validate one correspondence before expanding
Confirm that one returned item matches the intended segment. If a later address fails, record the result and lookup time rather than declaring the video deleted. AI can organize descriptions but cannot invent media addresses. Mark a saved-file task complete only after an actual save and verification.
Requests used in this project
- 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
- Get video playurl：https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_video_playurl · Documentation
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_user_post_videos_v2
| Parameter | Type | Required | Meaning |
|---|---|---|---|
uid |
string | Yes | User UID |
pn |
integer | No | Page number, no cap |
ps |
integer | No | Page size, max 100 |
keyword |
string | No | Keyword, empty returns all |
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_user_post_videos_v2"
params = {
"uid": "178360345"
}
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.
