You are preparing for a weekend market and follow the venue, organizer and transport accounts on Weibo. New posts arrive, but some only repeat an old poster. You need to know which update changes your preparation.

Verify who issued the notice

Look up account information using uid or custom as documented, then inspect the homepage. A familiar display name alone does not establish that an account represents the organizer. Save the profile, identifier and reason for following it, such as access arrangements or transport changes.

Separate posting time from event time

Retrieve posts by uid and retain lookup time. Use documented pagination information, including returned since_id where applicable, for the coverage you need. Verify event dates in the actual content instead of substituting publication time. A newly reposted image may still describe last week's event.

Extract changes that affect preparation

Your table can contain source, applicable date, notice subject, difference from the existing plan and person who should confirm it. Repeated promotion need not generate another reminder. Image details require reading or separate processing; the post list does not automatically interpret poster text. AI-assisted summaries should preserve dates and flag conflicting information.

Confirm important changes before acting on them

Maintain your own read, pending and incorporated statuses. Scheduling and alerts require a separate workflow. A post absent from a later batch is not necessarily withdrawn. Revisit the original or an official source before final arrangements. The output should show what needs changing and why, without turning an incomplete sample into an external announcement.

Requests used in this project

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.