Your home-improvement account contains photo sequences and video demonstrations. A folder full of links makes it difficult to find the material for one stage. Build a clear note index before deciding what to save.
Preserve source and coverage
Retrieve posted notes for the verified account using documented identifiers or sharing information. Keep cursors, page coverage and deduplicated note identifiers. Pinned items and newly published work should not be confused simply because of list position.
Choose details by content type
Use the image or video endpoint appropriately. The image endpoint returns only basic information such as covers for video notes, without playback links. Observe the documented precedence when supplying both note_id and a sharing link, and resolve uncertain types manually.
State the material status per note
Your index can contain source, project stage, content type, available media information, lookup time and next action. Reading text in pictures or understanding demonstrated steps needs separate inspection. Record only actual response information without assuming a universal media field or permanent address.
Complete archiving only after checking files
Detail retrieval is not automatic downloading, watermark removal or editing. Any later save must be checked against the correct source item before completion is recorded. AI can organize descriptions but should not invent filenames or claim quality checks. Deliver an accurate material index with remaining work visible rather than presenting a lookup as a complete local archive.
Requests used in this project
- 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_posted_notes
| 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 |
cursor |
string | No | Pagination cursor, leave empty for first request |
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_posted_notes"
params = {
"user_id": "61b46d790000000010008153",
"share_text": "http://xhslink.com/o/8GqargIxrko"
}
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.

