Xiaohongshu Comments API

Q: How do I get the replies under a comment?

This capability returns top-level comments only, and sub_comment_count tells you how many replies each has. To read them, call the Comment replies capability with the same note link and the comment's id.

Q: Does the order stay the same while paging?

Yes, as long as you keep the same sort. If you change sort, the next_page_token from the previous page no longer applies, so start again from the first page.

Q: Can I match commenters to note authors by ID?

Not directly. author_id on comment results usually uses a different form from the ID in note results and profile links. Before de-duplicating across batches, look it up with the Xiaohongshu Details capability, which reads the profile and returns one consistent user ID.

POST

API health

24h health: 96%
24h average time: 4.74 s

Healthy / normal
Available
Limited
Mostly down

Healthy

Last 24 hours

Last 30 days

Pull top-level comments on a Xiaohongshu note, 15 per page, with text, likes, IP location, commenter, reply count and author or AI-account flags. Order them with sort, page with page_token, and read the replies themselves through sub_comments.

Xiaohongshu Comments reads the top-level comments under one note, given the note's url. Each row carries the comment text, likes, publish time, IP region, the commenter's nickname and Xiaohongshu ID, and how many replies it has. Use it to see what readers say about a note: product feedback, sentiment around a launch, or how a seeding post landed.

Choose the order with sort (the platform default, newest or most liked), and pass next_page_token back as page_token for the next page. sub_comment_count gives only the number of replies; read the replies themselves with the Comment replies capability. is_author flags comments from the note's author and author_is_ai_agent flags accounts the platform marks as AI, so you can set both aside before scoring sentiment.

Price $5.56 per 1,000 requests ($0.005556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Xiaohongshu Comments endpoint (xiaohongshu/comments).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to xiaohongshu and action to comments, and put the parameters inside params.
- Required parameters:
  - url: Specifies the full Xiaohongshu note URL, formatted as /explore/<note_id> or /discovery/item/<note_id>. Use recent search URLs that retain query parameters like xsec_token.
- Optional parameters:
  - page_token: Pagination cursor for the comments, sub_comments, search, user_posts, search_users and hashtag actions: pass back the next_page_token value from a row of the previous response to fetch the next page.
  - sort: Comment order: default follows the platform's own order (the same as omitting it), newest puts the latest comments first, and most_liked puts the most-liked first. Keep the same value while paging. (allowed: default / most_liked / newest)
- Returns a list of records. Main fields of each record: id, text (Note body or comment text), like_count (Like count), posted_at, ip_location (IP location (province or country) that…), author_name, author_id (The author's user ID), sub_comment_count (Number of replies under this comment), note_id (Note ID), note_url (Link to the note the comment belongs to), next_page_token (Page token (search, comments, sub_comme…), images (Image links); 17 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=xiaohongshu.
- Example request body:
{
  "platform": "xiaohongshu",
  "action": "comments",
  "params": {
    "url": "https://www.xiaohongshu.com/explore/6aa7a3f600000000110335f8?xsec_token=YByFNzoKupps8B3qI774Gx7XGxfHpq4QWEvxU4zsD8454%3D"
  }
}
- Price: $5.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`xiaohongshu`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`comments`	Capability identifier, fixed value.
`url`	body.params	Not declared	Yes	-	Specifies the full Xiaohongshu note URL, formatted as /explore/<note_id> or /discovery/item/<note_id>. Use recent search URLs that retain query parameters like xsec_token. The sub_comments action requires both this url and a valid comment_id.
`page_token`	body.params	Not declared	No	-	Pagination cursor for the comments, sub_comments, search, user_posts, search_users and hashtag actions: pass back the next_page_token value from a row of the previous response to fetch the next page; omit it to start from the first page. Each page is one call, billed per request.
`sort`	body.params	`enum`	No	-	Comment order: default follows the platform's own order (the same as omitting it), newest puts the latest comments first, and most_liked puts the most-liked first. Keep the same value while paging; with a different value, the previous next_page_token no longer applies.Allowed values`defaultmost_likednewest`

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "xiaohongshu",
  "action": "comments",
  "params": {
    "url": "https://www.xiaohongshu.com/explore/6aa7a3f600000000110335f8?xsec_token=YByFNzoKupps8B3qI774Gx7XGxfHpq4QWEvxU4zsD8454%3D"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Real response

Captured October 15, 2026 at 15:16 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.

json

{
  "id": "req_…",
  "platform": "xiaohongshu",
  "action": "comments",
  "results": [
    {
      "id": "6aa80e9b000000000200c6ad",
      "text": "一点不像33平米的  感觉远不止  我住的45平在规划设计下 都很小",
      "like_count": 41,
      "posted_at": "2026-09-14T15:11:23+00:00",
      "author_name": "（已隐去）",
      "author_id": "（已隐去）",
      "sub_comment_count": 7,
      "note_id": "6aa7a3f600000000110335f8",
      "note_url": "https://www.xiaohongshu.com/explore/6aa7a3f600000000110335f8?xsec_token=YByFNzoKupps8B3qI774Gx7XGxfHpq4QWEvxU4zsD8454%3D",
      "next_page_token": "n1.6abba9cd000000001001c13b",
      "images": [],
      "is_author": false,
      "author_avatar_url": "https://sns-avatar-qc-ae.rednotecdn.com/（已隐去）",
      "author_red_id": "（已隐去）",
      "author_is_ai_agent": false,
      "platform": "xiaohongshu"
    },
    {
      "id": "6aa7dbde000000000a027007",
      "text": "房屋原博主有小红书吗",
      "like_count": 5,
      "posted_at": "2026-09-14T11:34:54+00:00",
      "author_name": "（已隐去）",
      "author_id": "（已隐去）",
      "sub_comment_count": 4,
      "note_id": "6aa7a3f600000000110335f8",
      "note_url": "https://www.xiaohongshu.com/explore/6aa7a3f600000000110335f8?xsec_token=YByFNzoKupps8B3qI774Gx7XGxfHpq4QWEvxU4zsD8454%3D",
      "next_page_token": "n1.6abba9cd000000001001c13b",
      "images": [],
      "is_author": false,
      "author_avatar_url": "https://sns-avatar-qc-ae.rednotecdn.com/（已隐去）",
      "author_red_id": "（已隐去）",
      "author_is_ai_agent": false,
      "platform": "xiaohongshu"
    }
  ],
  "next_page_token": …,
  "pagination": { … },
  "count": 10,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`id`	The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
`text`	Note body or comment text. note and hashtag return the full body; search and user_posts may return a truncated excerpt (up to about 60 and 100 characters respectively). Call note with the note ID for the full text.
`like_count`	Like count. On note and comment results, the likes on that item; on profile, the total likes the account's notes have received. null means not public or not returned this time, not zero.
`posted_at`	Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it.
`ip_location`	IP location (province or country) that Xiaohongshu displays; not entered by the user. Only some user_posts rows carry it.
`author_name`	Author's display name.
`author_id`	The author's user ID. Pass it to profile or user_posts. Note results carry the 24-character ID from profile URLs; comment results (comments, comments_batch, sub_comments) usually carry a different 29-character form. The two forms of one person do not match, so convert them with the user_id that profile returns before de-duplicating across batches.
`sub_comment_count`	Number of replies under this comment.
`note_id`	Note ID. Comment capabilities use it to point back to the note.
`note_url`	Link to the note the comment belongs to.
`next_page_token`	Page token (search, comments, sub_comments, user_posts, search_users, hashtag): pass it back unchanged as page_token, with the other parameters the same, to fetch the next page.
`images`	Image links. On note, hashtag, search and user_posts, every image of the note in order. On comment results (comments, comments_batch, sub_comments), the images attached to the comment, stickers included; an empty array means none. null means this item was not returned this time.
`is_author`	Whether the note's author wrote this comment. null means this item was not returned this time, not false.
`author_avatar_url`	The commenter's avatar link (comments, comments_batch, sub_comments).
`author_red_id`	The author's Xiaohongshu ID: on comment results (comments, comments_batch, sub_comments) the commenter's, on note the note author's.
`author_is_ai_agent`	Whether the commenter is an account the platform marks as AI; absent when this item was not returned.
`mentioned_users`	People @-mentioned: on comment results, those mentioned in the comment; on note, those mentioned in the note. Each entry has user_id and nickname. Absent when there are none.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

How do I get the replies under a comment?

This capability returns top-level comments only, and sub_comment_count tells you how many replies each has. To read them, call the Comment replies capability with the same note link and the comment's id.

Does the order stay the same while paging?

Yes, as long as you keep the same sort. If you change sort, the next_page_token from the previous page no longer applies, so start again from the first page.

Can I match commenters to note authors by ID?

Not directly. author_id on comment results usually uses a different form from the ID in note results and profile links. Before de-duplicating across batches, look it up with the Xiaohongshu Details capability, which reads the profile and returns one consistent user ID.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).