rednote/
comment-replies

The Rednote Comment Replies API collects one public page of replies beneath a known Rednote comment, with normalized text, authors, thread relationships, timestamps, and visible metrics.

Rednote Comment Replies API

Known comment
Nested replies
One source page
1 credit / request
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

Rednote Comment Replies

Rednote comment replies are public responses nested beneath a selected comment on a note, carrying reply text, author context, timestamps, and available relationship or engagement fields. The normalized records help teams inspect one known conversation branch without mixing the source comment identifier with stored-result pagination.

Rednote Comment Replies API Features

  • Paired thread referenceTarget a conversation branch with both the public note URL and the comment identifier that belongs to it.
  • Single-page reply captureEach Rednote Comment Replies API task runs one source request and saves the replies returned on that page without exposing a provider cursor or submit-time result limit.
  • Normalized reply bodyRead reply ID, public text, source URL, publication time, and collection time in the shared CommentItem shape.
  • Public author contextKeep available author ID, username, display name, profile URL, avatar, and account flags beside each reply.
  • Conversation relationshipsRetain available parent_id and post_id links together with visible like and reply counts for thread-aware processing.

Rednote Comment Replies API Parameters

ParametersRequiredDescription
urlRequiredRequired public URL whose host is xiaohongshu.com, xhslink.com, or a subdomain of either. This endpoint adds no path pattern or required xsec_token query rule.
comment_idRequiredRequired identifier for the source comment, using 1 to 256 ASCII letters, numbers, colons, underscores, or hyphens.

How to Use the Rednote Comment Replies API

Send the Rednote Comment Replies API a matching note URL and comment ID, then read the one-page reply result through SocQ's asynchronous task workflow.

  1. Choose a public xiaohongshu.com or xhslink.com note URL and verify a compatible comment ID from that same note.
  2. POST url and comment_id to /v1/rednote/comment-replies and retain the returned task_id.
  3. Poll GET /v1/tasks/{task_id} while the task is queued, running, or retrying; stop on succeeded or failed.
  4. After success, read data.results.items and use data.results.next_cursor only when paging reply rows already stored by SocQ.
curl -X POST "https://api.socq.ai/v1/rednote/comment-replies" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"url\":\"$REDNOTE_NOTE_URL\",\"comment_id\":\"$REDNOTE_COMMENT_ID\"}"

# Poll GET /v1/tasks/{task_id}
# Read data.results.items after status becomes succeeded

Rednote Comment Replies API Use Cases

  • Focused conversation review: Read public reply text and timestamps for one selected comment branch with the Rednote Comment Replies API instead of blending replies from an entire note.
  • Participant context enrichment: Associate each reply with available normalized author identity when preparing records for moderation research or manual review.
  • Thread relationship mapping: Use reply IDs with parent_id and post_id to reconnect stored records to their source comment and note when those fields are present.
  • Point-in-time response snapshots: Preserve collected_at beside visible like or reply counts so separate runs remain distinguishable observations.

Rednote Comment Replies API Pro Tips

  • Verify that comment_id belongs to the submitted note URL; the endpoint validates each field's format but does not establish that relationship before the source request.
  • Use a complete, public URL on xiaohongshu.com, xhslink.com, or an accepted subdomain even though this validator does not require a particular note path or xsec_token query parameter.
  • Keep comment_id within the accepted 1-to-256-character ASCII identifier pattern and do not substitute an internal database ID or SocQ task ID.
  • Treat a comment ID from another collection as conditional input: normalized comment IDs are optional, so confirm that a usable value is present before submitting it here.
  • Do not add results_limit or a source cursor to the submit payload; this endpoint performs one provider request for one source page.
  • Keep task-result next_cursor separate from comment_id because that cursor only pages normalized rows saved after the task succeeds.
  • Allow nullable identity, relationship, timestamp, and metric fields, and escape public reply text before rendering it in another product.

Explore other platforms

Combine Rednote data with public data from other supported social platforms.

Rednote Comment Replies API — FAQ

Rednote Comment Replies API collects one public source page of replies beneath a known Rednote comment, returning normalized reply, author, relationship, timestamp, and visible metric fields.

Both url and comment_id are required. The URL identifies the public Rednote note context, while comment_id selects the source comment whose nested replies are requested.

No endpoint-specific path or query rule is applied here. The runtime validator requires a parseable xiaohongshu.com or xhslink.com host, including their subdomains; a formally accepted but irrelevant URL can still fail at the source.

Use a verified public source record for a comment on the submitted note. A compatible upstream comment collection can expose a normalized id when the provider supplies one, but that field is optional and is not guaranteed on every record.

A CommentItem can contain ID, platform, resource, type, source URL, public text, author fields, parent_id, post_id, publication and collection times, plus visible likes_count and replies_count. Nullable fields remain null when unavailable.

No. The submit contract accepts neither field and makes one source request. After success, next_cursor can page through rows already stored under the SocQ task, but it does not continue the provider collection.

Each successful task costs a fixed 1 SocQ credit, independent of how many replies are saved from the source page.