--- title: "获取笔记二级评论列表/Get note sub comments" method: GET path: "/api/v1/xiaohongshu/app_v2/get_note_sub_comments" tags: ["Xiaohongshu-App-V2-API"] --- # 获取笔记二级评论列表/Get note sub comments `GET /api/v1/xiaohongshu/app_v2/get_note_sub_comments` ## Request - Base URL: `https://api.tikhub.io` (the document declares no server; this is the origin it was published from) - URL: `https://api.tikhub.io/api/v1/xiaohongshu/app_v2/get_note_sub_comments` - Auth: HTTP bearer # [中文] ### 用途: - 获取指定笔记某条评论下的子评论（回复）列表，使用游标分页 ### ⚠️ 计费提示: - 如果传入错误或不存在的笔记ID/评论ID（或分享链接解析失败），接口仍会正常响应，但 `data` 中会返回上游"服务异常"信息，该请求 **同样会正常计费扣费**，请在调用前确保参数有效。 ### 参数: - note_id: 笔记ID，如 "699916e6000000001d0253da" - share_text: 小红书分享链接，支持APP和Web端分享链接，支持 `xiaohongshu.com` 长链接、`xhslink.com` 和 `xhslink.cn` 短链接 - 优先使用`note_id`，如果没有则使用`share_text`，两个参数二选一，如都携带则以`note_id`为准。 - comment_id: 父评论ID（必需），如 "699fb9930000000008030db6" - cursor: 分页游标，首次请求留空，翻页时从上一次响应的 `$.data.data.cursor` 中提取 `cursor` 字段的值 - index: 分页索引，首次请求传 1，翻页时从上一次响应的 `$.data.data.cursor` 中提取 `index` 字段的值 ### 返回: - 子评论数据对象，包含子评论列表、分页游标等 ### 翻页说明: - 响应中的 `$.data.data.cursor` 是一个 JSON 对象，示例: `{"cursor":"69a0c134000000000c00910d","index":3}` - 首次请求：cursor留空，index传1 - 翻页请求：从 `$.data.data.cursor` 中提取 `cursor` 和 `index` 分别传入对应参数 # [English] ### Purpose: - Get sub-comment (reply) list under a specific comment of a note, using cursor pagination ### ⚠️ Billing Notice: - If a wrong or non-existent note ID / comment ID is passed (or the share link fails to parse), the endpoint still responds normally, but the `data` field will contain an upstream "service error" message. Such requests **will still be billed as normal**. Please make sure the parameters are valid before calling. ### Parameters: - note_id: Note ID, e.g. "699916e6000000001d0253da" - share_text: Xiaohongshu sharing link, supports APP and Web sharing links, including `xiaohongshu.com` full links, `xhslink.com` and `xhslink.cn` short links - Prefer to use `note_id`, if not, use `share_text`, one of the two parameters is required, if both are carried, `note_id` shall prevail. - comment_id: Parent comment ID (required), e.g. "699fb9930000000008030db6" - cursor: Pagination cursor, leave empty for first request, extract `cursor` value from `$.data.data.cursor` of previous response for next page - index: Pagination index, pass 1 for first request, extract `index` value from `$.data.data.cursor` of previous response for next page ### Return: - Sub-comments data object, including sub-comment list, pagination cursor, etc. ### Pagination Guide: - The `$.data.data.cursor` in response is a JSON object, e.g. `{"cursor":"69a0c134000000000c00910d","index":3}` - First request: leave cursor empty, pass index as 1 - Next page: extract `cursor` and `index` from `$.data.data.cursor` and pass them as corresponding parameters # [示例/Example] note_id="699916e6000000001d0253da" comment_id="699fb9930000000008030db6" ## Query parameters - `note_id` string: 笔记ID/Note ID - `share_text` string: 分享链接，支持xiaohongshu.com/xhslink.com/xhslink.cn/Share link, supports xiaohongshu.com, xhslink.com, xhslink.cn - `comment_id` string, required: 父评论ID/Parent comment ID - `cursor` string: 分页游标，首次留空，翻页时从$.data.data.cursor中提取cursor值/Pagination cursor, leave empty for first request, extract cursor from $.data.data.cursor for next page - `index` integer: 分页索引，首次传1，翻页时从$.data.data.cursor中提取index值/Pagination index, pass 1 for first request, extract index from $.data.data.cursor for next page ## Response `200` Successful Response - ResponseModel - `code` integer: HTTP status code | HTTP状态码 - `request_id` string, nullable: Unique request identifier | 唯一请求标识符 - `message` string: Response message (EN-US) | 响应消息 (English) - `message_zh` string: Response message (ZH-CN) | 响应消息 (中文) - `support` string: Support message | 支持消息 - `time` string: The time the response was generated | 生成响应的时间 - `time_stamp` integer: The timestamp the response was generated | 生成响应的时间戳 - `time_zone` string: The timezone of the response time | 响应时间的时区 - `docs` string, nullable: Link to the API Swagger documentation for this endpoint | 此端点的 API Swagger 文档链接 - `cache_message` string, nullable: Cache message (EN-US) | 缓存消息 (English) - `cache_message_zh` string, nullable: Cache message (ZH-CN) | 缓存消息 (中文) - `cache_url` string, nullable: The URL to access the cached result | 访问缓存结果的 URL - `router` string: The endpoint that generated this response | 生成此响应的端点 - `params` unknown - `data` unknown ## Other responses - `422`: Validation Error ## Changes - **2026-10-08** `96a122a5f220`: 2 info - added the optional property `detail/items/ctx` to the response with the `422` status - added the optional property `detail/items/input` to the response with the `422` status - **2026-09-01** `50f9ec6e1cd3`: 2 info - the `cache_message` response's property default value changed from `This request will be cached. You can access the cached result directly using the URL below, valid for 24 hours. Accessing the cache will not incur additional charges.` to `This response is cached and accessible via the URL below for 24 hours at no extra cost. The cache is for request tracing only — it doesn't affect the API's data freshness and won't be returned through the API again.` for the status `200` - the `cache_message_zh` response's property default value changed from `本次请求将被缓存，你可以使用下面的 URL 直接访问缓存结果，有效期为 24 小时，访问缓存不会产生额外费用。` to `本次响应已缓存，可通过下方 URL 直接查看，有效期 24 小时，访问缓存链接无额外费用。缓存仅用于请求溯源，不影响接口数据的时效性，也不会再次通过接口返回。` for the status `200` - **2026-04-14** `ee5b7c9c88f5`: 1 info - endpoint added [Operation history](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi/changes/api/v1/xiaohongshu/app_v2/get_note_sub_comments/get.md) --- [API](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi.md) - [All operations](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi/llms.txt) - [OpenAPI document](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi/revisions/86a3483c705a?raw)