Xiaohongshu Account Content List

Collect public Xiaohongshu account content with account identifiers, titles, and collection timestamps

Data collection Social Media General Web

Overview

Xiaohongshu account content offers a direct view of what an account publishes and how its public activity changes over time. This app turns the visible content associated with one account into a consistent record set, preserving the identifiers and timestamps that are useful for research, monitoring, and content planning.

The collection is useful when a profile page is too narrow a view. It keeps the account relationship, content identity, displayed title, publication time, and collection time together so teams can build an inventory, compare collection snapshots, and trace which public posts belong to a monitored account.

Data notes

The data comes from the public content list associated with the selected Xiaohongshu account. Records are returned from the source list and duplicate content IDs are removed across collected pages. Account identifiers, business identifiers, titles, and timestamps retain the source values; a source value can be unavailable and appear empty. Publication and collection timestamps are preserved as supplied, without inferring a timezone. Private, deleted, restricted, and login-only content is outside the coverage.

What the results look like

Each record represents one piece of public Xiaohongshu account content.

Content ID	Content title	Published at	Collected at	No data
6a86bf44000000002403fd59	去看了下智界RX，价格有点超预期...	2026-08-20T16:48:04	2026-08-27T10:25:46	No
6a844ebe00000000050306cf	鸿蒙系统怎么设置倾斜手机壁纸变色？	2026-08-18T20:23:26	2026-08-27T10:25:46	No

Additional values include Account ID, Account unique ID, Business ID, Source account item, and the source no-data marker.

Use cases

Build a publishing inventory by grouping Content ID and Content title under Account ID, then compare Published at across repeated collections.
Monitor posting cadence by counting records by Published at and checking whether the visible activity of an account is increasing or slowing.
Trace collection freshness by comparing Published at with Collected at when reviewing a monitored account.
Separate empty-result outcomes from normal content by checking No data together with Source account item.

Scope and boundaries

Each run processes one Xiaohongshu account ID and accepts an expected count from 1 to 20,000. Results are returned in complete batches of 20, so the actual count may be rounded up. Up to 1,000 result pages are protected per run, and only publicly visible content is covered.

Good for
When you need a public content list for a specific Xiaohongshu account
When you need post identifiers, titles, publication times, and collection times for content analysis

Do not use for
When you need private, deleted, restricted, or login-only content
When you need an instant single-record lookup rather than a collected list

Failure handling

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

1If no data is returned, verify the account ID and confirm that the account has publicly visible content
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.

Field	Business name	Type	Required	Default	Enum / Constraints	Example	Description
account_id	Xiaohongshu account ID	string	Yes	—	—	6366a311000000001f01fd6c	The Xiaohongshu account ID whose public content should be collected. Enter 1 to 512 characters.
crawl_num	Expected content count	integer	Yes	—	1–20000	20	The expected number of content records to collect. Results are returned in complete batches of 20, so the actual count may be rounded up; values above 20,000 are not accepted.

Output

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

Field	Business name	Type	Example	Description
account_id	Account ID	string	6366a311000000001f01fd6c	The Xiaohongshu account identifier associated with the content record; the source may return null.
account_unique_id	Account unique ID	string	xiaohongshu_account_example	The account's unique identifier supplied by the source; it may be null when unavailable.
biz_id	Business ID	string	6366a311000000001f01fd6c	The business identifier carried by the source record; it may be null.
content_id	Content ID	string	6a86bf44000000002403fd59	The content identifier used to distinguish records across result pages; it may be null in source data.
content_title	Content title	string	去看了下智界RX，价格有点超预期...	The title or displayed text of the public Xiaohongshu content; it may be null.
crawl_time	Collected at	string	2026-08-27T10:25:46	The source timestamp when the content was collected, without an inferred timezone; it may be null.
publish_time	Published at	string	2026-08-20T16:48:04	The source timestamp when the content was published, without an inferred timezone; it may be null.
source_item	Source account item	string	6366a311000000001f01fd6c	The account item associated with the result, copied from the task metadata.
no_data	No data	boolean	false	Whether the task metadata marks this account result as having no public data.

Record schema

Output is returned record by record. detail.output.idFieldHint

output.schema

{
  "type": "object",
  "properties": {
    "account_id": {
      "type": "string",
      "title": "Account ID",
      "description": "The Xiaohongshu account identifier associated with the content record; the source may return null.",
      "prefill": "6366a311000000001f01fd6c"
    },
    "account_unique_id": {
      "type": "string",
      "title": "Account unique ID",
      "description": "The account's unique identifier supplied by the source; it may be null when unavailable.",
      "prefill": "xiaohongshu_account_example"
    },
    "biz_id": {
      "type": "string",
      "title": "Business ID",
      "description": "The business identifier carried by the source record; it may be null.",
      "prefill": "6366a311000000001f01fd6c"
    },
    "content_id": {
      "type": "string",
      "title": "Content ID",
      "description": "The content identifier used to distinguish records across result pages; it may be null in source data.",
      "prefill": "6a86bf44000000002403fd59"
    },
    "content_title": {
      "type": "string",
      "title": "Content title",
      "description": "The title or displayed text of the public Xiaohongshu content; it may be null.",
      "prefill": "去看了下智界RX，价格有点超预期..."
    },
    "crawl_time": {
      "type": "string",
      "title": "Collected at",
      "description": "The source timestamp when the content was collected, without an inferred timezone; it may be null.",
      "prefill": "2026-08-27T10:25:46"
    },
    "publish_time": {
      "type": "string",
      "title": "Published at",
      "description": "The source timestamp when the content was published, without an inferred timezone; it may be null.",
      "prefill": "2026-08-20T16:48:04"
    },
    "source_item": {
      "type": "string",
      "title": "Source account item",
      "description": "The account item associated with the result, copied from the task metadata.",
      "prefill": "6366a311000000001f01fd6c"
    },
    "no_data": {
      "type": "boolean",
      "title": "No data",
      "description": "Whether the task metadata marks this account result as having no public data.",
      "prefill": false
    }
  },
  "required": [],
  "additionalProperties": false
}

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.

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": {
    "meme_today__xiaohongshu-account-list": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=meme_today/xiaohongshu-account-list",
      "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

20 returned records

Charged by the number of records successfully returned. Failed runs are not charged. Billed in units of 20 record; any partial unit is rounded up to 20 record.

$0.01/ 20 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

Xiaohongshu account IDaccount_id*The Xiaohongshu account ID whose public content should be collected. Enter 1 to 512 characters.

Expected content countcrawl_num*The expected number of content records to collect. Results are returned in complete batches of 20, so the actual count may be rounded up; values above 20,000 are not accepted.

Please fill in the required parameters first

From $0.01 / 20 record