Readers keep asking what to do in special cases under your Xiaohongshu tutorial. You want the follow-up to address real confusion. Comments provide concrete questions, but the collection method affects which voices you see.
Separate recent questions from highly liked ones
The documentation supports newest-first and like-count ordering, and warns that default sorting may lose or duplicate comments during pagination. Use recent ordering to investigate emerging questions, then examine liked comments as a separate sample. If both a note ID and share link are supplied, the ID takes precedence, so confirm the intended note.
Carry the complete continuation state
Subsequent requests depend on the returned cursor, index, and folding state. Changing only one does not establish continuous coverage. Retain source associations, check duplicates, and record where reading stopped. Missing pages or folded material limit what you can claim about the discussion.
Translate remarks into production tasks
Distinguish procedural questions, alternative materials, experience reports, and praise. Group related questions while preserving meaningful conditions: space limitations and budget limitations may require different answers. For each proposed follow-up, specify the step to explain, the demonstration required, and anything still needing investigation. Commenters are a self-selected sample, not every reader who struggled with the tutorial.
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_note_comments
| Parameter | Type | Required | Meaning |
|---|---|---|---|
note_id |
string | No | Note 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 |
index |
integer | No | Comment index, pass 0 for first request |
pageArea |
string | No | Expansion state: UNFOLDED (default) or FOLDED |
sort_strategy |
string | No | Sort strategy: default, latest_v2, like_count |
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_note_comments"
params = {
"note_id": "697c0eee000000000a03c308",
"share_text": "http://xhslink.com/o/8GqargIxrko",
"index": "0",
"pageArea": "UNFOLDED",
"sort_strategy": "latest_v2"
}
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.

