Rednote Note Comments
Rednote note comments are public responses associated with a specific note and can include the response text, author identity, publication time, thread reference, and visible interaction counts. They help researchers preserve what people said around a chosen note while keeping each observation linked to its source and collection time.
Features
- Flexible Rednote share-link inputSubmit one reference hosted on xiaohongshu.com, xhslink.com, or a subdomain; the note-comments validator does not require a particular path, query string, or xsec_token.
- Stable comment recordsReceive comment IDs, text, source URLs, timestamps, and available author identity in the normalized CommentItem 1.0 result shape.
- Note and thread referencesRetain post_id and parent_id when supplied so returned comments can stay associated with their note and available parent context.
- Point-in-time engagement fieldsKeep available likes_count and replies_count beside collected_at without converting missing values into zero or implying complete reply coverage.
Parameters
| Parameters | Required | Description |
|---|---|---|
url | Required | Required non-empty reference. Runtime validation accepts xiaohongshu.com, xhslink.com, and their subdomains without enforcing a pathname or requiring xsec_token; use an actual note share link so the provider can resolve the intended note. |
How to Use
Submit one supported Rednote note link, follow the asynchronous task, and read its stored normalized comments.
- Copy an actual Rednote note share link on xiaohongshu.com or xhslink.com.
- POST url to /v1/rednote/note-comments and save the returned task_id.
- Poll /v1/tasks/{task_id} until the task succeeds or reports a failure.
- Read data.results.items; follow next_cursor only when has_more is true to page through stored task results.
curl -X POST "https://api.socq.ai/v1/rednote/note-comments" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://xhslink.com/{share_code}"}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueBest Use Cases
- Qualitative response coding: Review returned public text and available author context to organize questions, reactions, or recurring discussion themes around one selected note.
- Source-linked comment archives: Preserve comment IDs, source URLs, post_id, parent_id, published_at, and collected_at for traceable research records.
- Engagement snapshot review: Compare available like and reply counts across returned comments while anchoring every observation to its collection time.
Pro Tips
- Use the complete share link copied for the intended note; passing hostname validation alone does not guarantee that the provider can resolve an unrelated path.
- Do not invent or separately require xsec_token. That rule belongs to the note-detail contract, not rednote/note-comments.
- Do not send results_limit or a provider cursor: the submission owns only url and makes one source request.
- Treat parent_id, post_id, timestamps, author attributes, and metrics as nullable source fields rather than guaranteed values.
- Keep source collection depth separate from next_cursor, which only paginates normalized records already stored for a completed task.
Related APIs
Use these APIs when you need a different type of public Rednote data.