You are reviewing a Weibo account's recent content, but an older spreadsheet does not explain how it was collected. The post-list capability offers different detail levels with different batch sizes. Establish a consistent method before comparing activity.

Choose a detail level suited to the review

The documented feature settings distinguish basic, extended, image-related, and complete data. Select according to the material needed and record the choice. One page under one setting is not equivalent to one page under another, and page count is not a natural time measure.

Continue with traceable pagination

Pages begin at one, and responses provide a continuation identifier. Follow the documented behavior while retaining request conditions and returned positions. Check identities across batches for duplicates and record coverage. Do not assume every item in a user's post list is original content without examining its nature.

Discuss content rather than collection artifacts

Filter the intended period using confirmed publication information, then review topics, formats, and activities. Leave missing dates or text pending. Media information can support format classification without explaining performance. Present the verified content inventory, editorial observations, and collection limits. Unretrieved records do not demonstrate inactivity, and differences between snapshots do not automatically establish a strategy change.

Request URL and parameters

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

Parameter Type Required Meaning
uid string Yes User id
page integer No Page number
feature integer No Feature type: 0=10 basic posts, 1=20 extended posts, 2=20 image-related posts, 3=20 video-related posts, fields increase progressively
since_id string No Pagination identifier for getting next page data

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_posts"
params = {
    "uid": "7277477906",
    "page": "1",
    "feature": "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.