Build a reading path through a Weibo author’s visible videos

Decide what the reader wants to understand

An author may publish interviews, event footage, and brief explanations together. Use uid to retrieve the video list, then define the guide’s question, such as understanding how an exhibition was prepared. Details can include titles, covers, and play counts, but these do not automatically establish story order or show that every video concerns the same event.

Continue with the returned pagination state

The request uses cursor, while next_cursor and has_more guide subsequent pages. A title referring to all videos does not mean one request supplies every historical work. Actual coverage depends on the pages read and material visible at that time. Preserve inspected sources and check duplicates rather than letting a larger count disguise incomplete reading.

Connect selected works with viewing reasons

For a hypothetical sequence covering installation, opening, and visitor discussion, explain what each work helps the reader understand. This is your editorial structure, not an automatically recognised event timeline. A play count is an observed value, not proof that every viewer finished or agreed. State the guide’s date and scope and identify missing context. The result should be a usable, honest route through the material rather than a historical narrative invented by joining titles together.

Request URL and parameters

GET https://api.trmesh.com/openapi/api/v1/weibo/web_v2/fetch_user_video_list

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/weibo/web_v2/fetch_user_video_list"
params = {
    "uid": "7277477906",
    "cursor": "0"
}
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.