Start with the account instead of guessing a room

When following a creator’s online demonstration, you may only have the account’s sec_uid. This operation accepts that identifier to retrieve live-stream data. It is useful for an account-based check, but sec_uid is not a nickname or an arbitrary number copied from a page. Verify the intended account first so a successful request is not mistaken for finding the right broadcaster.

Interpret one response as one observation

Work with the live data actually returned rather than assuming playable material must exist. A creator may not have started or may already have finished. One request is not a continuous availability record. If a hypothetical evening session is checked in the afternoon, missing expected information should prompt a schedule check rather than a declaration that broadcasting has stopped permanently.

Leave a trail another viewer can follow

Your preparation record might contain the account identifier, public event source, check time, and next question to confirm. Any schedule in that record comes from your event information, not an automatically generated timetable. Live media details do not grant recording rights or promise a replay. In a handoff, explain that the account entry point was checked and that status can change, allowing the next person to revisit the same target instead of guessing room identifiers.

Request URL and parameters

GET https://api.trmesh.com/openapi/api/v1/douyin/web/fetch_user_live_videos_by_sec_uid

Parameter Type Required Meaning
sec_uid string Yes User sec_uid

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/douyin/web/fetch_user_live_videos_by_sec_uid"
params = {
    "sec_uid": "MS4wLjABAAAAAIKOBr_x6p2fPVKOAhqG8LrC1lwwdWChifKEsl-TXFS-kGSGqpMBRexJdzoAfvUF"
}
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.