logo
EN

Xiaohongshu Note Details

Provide Xiaohongshu note IDs to retrieve structured note, author, media, and timestamp details

Data collection
Developer
meme_today
Pricing
From $0.0055 / record
Last updated
2026-09-22

Overview

Turn a list of known Xiaohongshu note IDs into a structured dataset of note details. Each record represents one successfully processed note and brings together the publishing account, title, full text, content type, source and cover links, publication time, and collection time. It is designed for teams that already know which notes matter and need consistent rows for research, reporting, or content review.

Note-level data is most useful when the visible text and media references can be compared side by side. This app removes the work of collecting each note manually while preserving the relationship between a note, its author, its format, and its timestamps.

Data notes

The dataset contains details returned for successfully processed Xiaohongshu notes. Records are deduplicated by Note ID, and each valid unique input ID returns at most one detail record. Duplicate, invalid, unavailable, or failed IDs can result in fewer records than were submitted. Note Text preserves the returned body and hashtags, while Content Type keeps the source code such as video or normal. Published At and Collected At are source-provided timestamps; the source documentation does not specify their timezone. Except for Note ID, any detail field may be null when the source has no value. Notes that cannot be accessed or processed are not represented as detail records.

What the results look like

Each record represents one Xiaohongshu note:

Note IDNote TitleAccount NameContent TypePublished At
6a77168d0000000008011cb5云股东们，陀螺双面磁吸支架，做不做？优篮子Ulanzi老板video2026-08-08T19:44:13
6a82b49a000000002403dc1d如何选对长期主义好物：30+中女的经验之谈者来美女normal2026-08-17T17:31:11

The result also includes Account ID, Note Text, Note URL, Cover URL, and Collected At.

Use cases

  • For creative analysis, compare Note Title, Note Text, and Content Type to identify recurring themes and format choices.
  • For account research, group records by Account ID and Account Name to review what each publisher discusses.
  • For publishing timelines, order notes by Published At and compare that sequence with Collected At to organize monitoring snapshots.

Scope and boundaries

Up to 200 Xiaohongshu note IDs per run; each valid unique ID returns at most one detail record.

  • Good for
  • Use when you already have Xiaohongshu note IDs and need structured note details in bulk
  • Use when research needs note text, author identity, content type, media links, and timestamps in one dataset
  • Do not use for
  • Do not use to discover notes by keyword or account when note IDs are unknown
  • Do not use when comments, likes, saves, or other engagement metrics are required

Failure handling

Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.

  1. 1Retry unchanged after temporary service or rate-limit failures
  2. 2Invalid, unavailable, duplicate, or failed note IDs can yield fewer records than submitted; remove known invalid IDs before retrying
  3. 3Split lists into runs of no more than 200 note IDs

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

  • Xiaohongshu note listnote_itemsRequiredarray<object>
    The Xiaohongshu notes to retrieve, with one note ID in each item; enter 1 to 200 items per run.
    Itemsup to 200 itemsExample[{"noteId":"6a77168d0000000008011cb5"}]

Output

Field structure of a single record, generated from the output.schema in manifest.json.

  • Account IDaccountIdstring
    Identifier of the account that published the note; may be null when unavailable.
    Example55c8ae2762a60c7e4bb45331
  • Account NameaccountNamestring
    Display name of the account that published the note; may be null when unavailable.
    Example优篮子Ulanzi老板
  • Note IDcontentIdstring
    Unique identifier of the Xiaohongshu note; guaranteed non-null for successfully returned records.
    Example6a77168d0000000008011cb5
  • Note TextcontentTextstring
    Full text returned for the note, including hashtags when present; may be null when unavailable.
    Example我们做了一个双面磁吸支架，但是它是一个陀螺仪。相比我们之前做的双面磁吸支架，这个陀螺仪更加好玩和解压。能在手上转，能吸手机，能吸机位，配合吸盘还能吸车里、吸镜子上。 这个支架，竖拍仰拍直接搞定，桌面支架 + 拍摄支架一个就够。 大家觉得这个产品我们要不要做？欢迎在评论区留言你的建议。 #优篮子[话题]# #Ulanzi[话题]# #陀螺仪[话题]# #磁吸[话题]# #手机支架[话题]# #手机拍摄[话题]# #手机支架[话题]# #创作者必备[话题]#

Sample data

Generated from output.schema. Fields without a sample value use structural placeholders.

output.example
{
  "accountId": "55c8ae2762a60c7e4bb45331",
  "accountName": "优篮子Ulanzi老板",
  "contentId": "6a77168d0000000008011cb5",
  "contentText": "我们做了一个双面磁吸支架，但是它是一个陀螺仪。相比我们之前做的双面磁吸支架，这个陀螺仪更加好玩和解压。能在手上转，能吸手机，能吸机位，配合吸盘还能吸车里、吸镜子上。\n这个支架，竖拍仰拍直接搞定，桌面支架 + 拍摄支架一个就够。 大家觉得这个产品我们要不要做？欢迎在评论区留言你的建议。\n#优篮子[话题]# #Ulanzi[话题]# #陀螺仪[话题]# #磁吸[话题]# #手机支架[话题]# #手机拍摄[话题]# #手机支架[话题]# #创作者必备[话题]#",
  "contentTitle": "云股东们，陀螺双面磁吸支架，做不做？",
  "contentTypeCode": "video",
  "contentUrl": "https://www.xiaohongshu.com/discovery/item/6a77168d0000000008011cb5",
  "coverUrl": "https://sns-i11.rednotecdn.com/spectrum/1040g34o323jvncmi74104129jvn2ekphjhs3jm8",
  "crawlTime": "2026-08-17T20:25:21",
  "publishTime": "2026-08-08T19:44:13"
}

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 config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=meme_today/xiaohongshu-detail",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}
View my API Keys →

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. (The prompt asks the AI to request your API key from you, so credentials never end up in chat history or shared configs.)

detail.access.mcp.composeHint

Pricing

returned note detail

Charged by the number of records successfully returned. Failed runs are not charged.

$0.0055/ record
Per task submitted

Charged once per submitted run, regardless of how many records are returned.

$0.0001/ run

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
From $0.0055 / record