A friend sends a restaurant video, but you cannot tell whether it shows the branch you plan to visit. Retrieve the specific post first, then decide whether its associated location or merchant information will help resolve the question.

Start with the video identifier

The required parameter is aweme_id. Preserve the original source link and do not substitute an author ID or restaurant name. Inspect one response before expanding your list. A video-detail lookup is not a service for verifying current restaurant opening hours.

Request anchors for a concrete reason

need_anchor_info defaults to false. The documentation says enabling it may provide anchors such as locations, merchants or product showcases and may increase response time. Leave it off for a basic reference card. Enable it when associated merchant information is relevant, while remembering that an anchor is not guaranteed and does not establish current stock or queue conditions.

Inspect unavailable results even after HTTP 200

Deleted or restricted videos can still return HTTP 200, retain filter_detail and be charged normally. Do not mark a record complete merely because the transport status is successful. Check the content result and preserve the unavailable-content explanation. Repeated calls do not themselves resolve deletion or access restrictions.

Leave a branch-checking note

Useful worksheet columns include source, lookup time, anchor option, visible merchant clues, branch to verify and result status. A note such as “branch identity needs confirmation; check opening hours separately” accurately describes the remaining work. If an error occurs with anchors enabled, the documentation suggests trying with the option disabled. Record that difference so another reader understands what information was omitted.

Request URL and parameters

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

Parameter Type Required Meaning
aweme_id string Yes Video id
need_anchor_info boolean No Whether anchor information is needed

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_one_video"
params = {
    "aweme_id": "7372484719365098803",
    "need_anchor_info": "false"
}
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.