Several Weibo accounts have entered a monitoring sheet, and the team wants to understand who they are. Detailed user information can support background reading, but a nickname alone cannot classify an account as an institution or an expert.

Choose a clear lookup basis

The capability accepts a user ID or a custom username. Use one and retain the original discovery source. Confirm that the returned object matches that lead. Similar avatars and biographies can cause confusion, so unresolved accounts should not be merged into an established subject's history.

Interpret biography and scale separately

The documentation describes nickname, avatar, biography, following count, and follower count among the details. Fill only available fields. A biography is an account's own presentation, not proof of an organizational relationship. Follower numbers provide scale context without establishing the reach of any individual post or the quality of relationships.

Make the card useful for further reading

Add the observation date, confirmed identity clues, and remaining questions. Assessing viewpoints requires separate reading of posts; a profile is not a complete opinion sample. Preserve earlier observations when details change so old research retains its context. Colleagues should be able to distinguish information ready to cite from judgments that remain working hypotheses.

Request URL and parameters

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

Parameter Type Required Meaning
uid string / null No User id
custom string / null No Custom Weibo username

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_info"
params = {
    "uid": "1722594714",
    "custom": "shuqi"
}
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.