A screenshot shows a reader complaining that a Xiaohongshu tutorial skips a step. The author appears to have replied, but the screenshot cuts off. Read the relevant reply chain before deciding whether the issue remains unanswered.

Match the parent comment to the note

This capability requires a parent-comment ID together with the note reference. The note ID takes precedence over a share link when both are supplied. Preserve the parent comment and its source before retrieving replies. Similar wording in another thread does not make it part of this conversation.

Use reply-specific continuation state

The documentation starts replies with an empty cursor and an index of one, then uses cursor and index values from the specified response location. Do not reuse first-level comment initialization blindly. Keep parent associations across pages and record interruptions or duplicates.

Separate questions, explanations, and follow-ups

Read which remark each reply addresses, checking the page when necessary. An author's clarification may alter the meaning of the initial complaint. Agreement from another user is not necessarily another firsthand experience. Summarize what was raised, what was clarified, and what remains unresolved. Visible replies do not guarantee coverage of deleted, unavailable, or uncollected material, so keep the conclusion within the observed conversation.

Request URL and parameters

GET https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_note_sub_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
comment_id string Yes Parent comment ID
cursor string No Pagination cursor, leave empty for first request, extract cursor from $.data.data.cursor for next page
index integer No Pagination index, pass 1 for first request, extract index from $.data.data.cursor for next page

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_sub_comments"
params = {
    "note_id": "699916e6000000001d0253da",
    "share_text": "http://xhslink.com/o/8GqargIxrko",
    "comment_id": "699fb9930000000008030db6",
    "index": "1"
}
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.