Give one WeChat Video Account keyword and a maximum result count to get matching public videos, publishers, engagement counts, and timestamps.
Xiaohongshu Note Comments
Collect public comments, engagement details, author information, and timestamps from one Xiaohongshu note
Overview
Public comments on a Xiaohongshu note reveal how readers respond in their own words, which details attract attention, and where follow-up discussion develops. This Data App turns the public comment area of one note into a consistent dataset containing comment text, author details, reply relationships, engagement snapshots, media references, visible location text, and timestamps.
The result is designed for repeatable analysis instead of manual scrolling. It preserves the original wording and connects each comment to its note and discussion thread, making reactions easier to compare across collection runs and helping teams inspect both top-level comments and replies with the same set of fields.
Data notes
The data covers comments and author details that are publicly visible for the supplied Xiaohongshu note at collection time. Each normal record is identified by its Comment ID, which removes duplicates across collected pages. Private, deleted, restricted, and login-only comments are outside the coverage.
Like count, Reply count, View count, account details, and visible location values are snapshots and may change after collection. Count values and classification codes are retained as source text where supplied that way. Comment images are retained in the source text form supplied with each record, while Comment voice URL points to an audio attachment when one is available. Published at and Collected at preserve the source timestamps without inferring a timezone. Source note ID and No data retain the collection outcome when a note has no public comment result.
What the results look like
Each normal record represents one publicly visible comment from the selected Xiaohongshu note.
| Comment ID | Comment text | Account name | Published at | Like count | Reply count |
|---|---|---|---|---|---|
| 6a8f8242000000000202b5d5 | 已经是了 都赖国产车 减配吹牛逼 | 四海 | 2026-08-27T08:18:11 | 0 | 0 |
| 6a8f8242000000000202b5d6 | 这款颜色很耐看,通勤也方便 | 小林 | 2026-08-27T08:25:42 | 3 | 1 |
Additional values include account and avatar identifiers, location text, note and comment relationships, image and voice references, recognized speech and on-screen text, collection time, and the no-data marker.
Use cases
- Compare Comment text with Like count and Reply count to identify reactions that generated stronger visible engagement.
- Group Comment text by recurring phrases, then use Published at to see how the discussion changed over time.
- Reconstruct discussion threads with Parent comment ID, Root comment ID, Comment level, and Reply cursor to separate top-level reactions from follow-up conversations.
- Review Account name, Public account ID, IP region, Location cities, and Location provinces to describe visible participant signals without treating them as verified identity data.
Scope and boundaries
Each run accepts one Xiaohongshu note ID and an expected comment count from 1 to 100. Results are returned in complete batches of 10, so the actual count may be rounded up. Only publicly available comments are covered.
- Good for
- When you need public comment text and engagement details from a specific Xiaohongshu note
- When you need comment authors, reply relationships, timestamps, and visible location text for analysis
- Do not use for
- When you need comments from a platform other than Xiaohongshu
- When you need private, deleted, restricted, or login-only comments
Failure handling
Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.
- 1If no comments are returned, verify the note ID and confirm that the note and its comments are publicly visible
- 2Retry later after rate limiting, temporary service unavailability, or a timeout
- 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
- 4If authentication fails, verify the API Key configured for the execution environment
Input
Parameters required to call this App, generated from the input.schema in manifest.json.
- Xiaohongshu note ID
note_idRequiredstringThe identifier of the Xiaohongshu note whose public comments will be collected. Enter one note ID only, not a keyword or URL.Example6a6c063d000000002500e938 - Expected comment count
comment_countRequiredintegerThe expected number of comments to collect, from 1 to 100. Results are returned and billed in complete batches of 10, so the actual count may be rounded up.Range1–100Example10
Output
Field structure of a single record, generated from the output.schema in manifest.json.
- Account ID
account_idstringThe Xiaohongshu account identifier associated with the comment authorExample58f9dce250c4b44bf45e0263 - Account name
account_namestringThe public display name of the comment authorExample四海 - Public account ID
account_public_idstringThe public-facing Xiaohongshu identifier of the comment authorExamplexiaohongshu_user_58f9dce2 - Location cities
accurate_location_citiesstringCity-level location text associated with the comment author when availableExample南京
Sample data
Generated from output.schema. Fields without a sample value use structural placeholders.
{
"account_id": "58f9dce250c4b44bf45e0263",
"account_name": "四海",
"account_public_id": "xiaohongshu_user_58f9dce2",
"accurate_location_cities": "南京",
"accurate_location_provinces": "江苏",
"asr_text": "城市通勤体验分享",
"avatar_url": "https://sns-avatar-qc.xhscdn.com/avatar/61b3eba96564fffada47f01e.jpg?imageView2/2/w/120/format/jpg",
"biz_id": "6a8bfb930000000033020097",
"comment_id": "6a8f8242000000000202b5d5",
"comment_image_url": "[]",
"comment_level": 1,
"comment_text": "已经是了 都赖国产车 减配吹牛逼",
"comment_type_code": "1",
"comment_voice_url": "https://sns-video-qc.xhscdn.com/comment/voice/6a8f8242000000000202b5d5.m4a",
"content_id": "6a8bfb930000000033020097",
"content_url": "https://www.xiaohongshu.com/explore/6a8bfb930000000033020097",
"crawl_time": "2026-08-27T17:39:26",
"like_count": "0",
"ocr_text": "城市通勤",
"parent_comment_id": "6a8f8242000000000202b5d5",
"publish_ip_region_name": "江苏",
"publish_time": "2026-08-27T08:18:11",
"reply_count": "0",
"root_comment_id": "6a8f8242000000000202b5d5",
"sub_comment_cursor": "0",
"source_note_id": "6a8bfb930000000033020097",
"no_data": false,
"view_count": "0"
}Integration
This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.
With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.
Client config
Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=meme_today/xiaohongshu-note-comments",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Let AI set it up for you
Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)
detail.access.mcp.composeHint
Pricing
Charged by the number of records successfully returned. Failed runs are not charged. Billed in units of 10 records; any partial unit is rounded up to 10 records.
Charged once per submitted run, regardless of how many records are returned.
Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.
View creditsTry it now
Fill in the parameters and run. Results come from a real call.