Your account mixes rental improvements, cooking and everyday shopping. Each note may work individually, but a new reader may not know what following you will provide. Review whom the recent work helps rather than assigning the account a vague health score.
Fix the account and observation window
Use the profile and posted-note interfaces with verified identifiers or sharing information. Choose a clear period and retain actual coverage. Separate pinned older notes from recent publications instead of confusing placement with recency.
State one reader benefit per note
Retrieve image and video details through the appropriate endpoints. After reviewing each note, describe the problem it addresses. Personal records need not be forced into a utility claim. These interpretations are your analysis, not diagnostic fields returned by the API.
Compare directions with their production effort
Your table can include source, intended reader, useful outcome, material effort and willingness to continue. A promising subject may still demand more filming time than you can sustain. Available engagement describes an observation, not private audience characteristics or income. Differently aged cumulative counts need care.
Choose a realistic promise for the next phase
Select a problem you want to keep answering and plan a few follow-ups. AI can group notes or refine a positioning sentence but cannot guarantee growth. Try the direction before making sweeping changes to past work. Finish with a content map, a concrete next plan and clearly identified assumptions to observe.
Requests used in this project
- Get user info:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_user_info · Documentation
- Get user posted notes:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_user_posted_notes · Documentation
- Get image note detail:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_image_note_detail · Documentation
- Get video note detail:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_video_note_detail · Documentation
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_user_info
| Parameter | Type | Required | Meaning |
|---|---|---|---|
user_id |
string | No | User ID |
share_text |
string | No | xhslink.com/xhslink.cn/Share link, supports xiaohongshu.com, xhslink.com, xhslink.cn |
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/xiaohongshu/app_v2/get_user_info"
params = {
"user_id": "61b46d790000000010008153",
"share_text": "https://xhslink.com/m/3ZSCJZAMz0a"
}
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.

