Xiaohongshu Account Content List
Collect public Xiaohongshu account content with account identifiers, titles, and collection timestamps
Original · en-USVolver a la traducción
Descripción general
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.
Alcance y límites
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.
- Adecuada para
- 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
- No usar para
- When you need private, deleted, restricted, or login-only content
- When you need an instant single-record lookup rather than a collected list
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el autor. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 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
Entrada
Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.
| Campo | Nombre de negocio | Tipo | Obligatorio | Predeterminado | Enum / Restricciones | Ejemplo | Descripción |
|---|---|---|---|---|---|---|---|
| account_id | Xiaohongshu account ID | string | Sí | — | — | 6366a311000000001f01fd6c | The Xiaohongshu account ID whose public content should be collected. Enter 1 to 512 characters. |
| crawl_num | Expected content count | integer | Sí | — | 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. |
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
| Campo | Nombre de negocio | Tipo | Ejemplo | Descripción |
|---|---|---|---|---|
| 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. |
Schema del registro
La salida se devuelve registro a registro. detail.output.idFieldHint
{
"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
}Integración
Esta App se puede integrar mediante MCP, API, SDK o exportación de archivos — todos los canales comparten las mismas capacidades y precios. Cada solicitud se autentica con la cabecera Authorization: Bearer usando una API Key (de larga duración, creada en la consola de Data Hub); los clientes MCP también pueden iniciar sesión con OAuth sin clave. Más opciones como CLI y Skill están en camino.
Con MCP (Model Context Protocol) puedes llamar a esta App directamente desde clientes de IA como Claude y Cursor. Elige tu cliente y el modo de autenticación, y copia la configuración de abajo.
Configuración del cliente
Sustituye el valor tras Bearer por tu API Key de larga duración. Funciona en cualquier cliente, CI o entorno sin interfaz.
{
"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>" }
}
}
}Deja que la IA lo configure por ti
¿No quieres editar configuraciones a mano? Copia el prompt de instalación y pégalo en cualquier cliente de IA: completará la configuración a su manera. (El prompt le pide a la IA que te solicite tu API Key, de modo que las credenciales nunca queden en el historial de chat ni en configuraciones compartidas.)
detail.access.mcp.composeHint
Precios
Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran. Se factura en unidades de 20 registro; cualquier unidad parcial se redondea a 20 registro.
Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.
Los distintos eventos de facturación se acumulan de forma independiente. Consulta cada elemento para más detalles. Las ejecuciones fallidas no se cobran.
Ver créditosPruébalo ahora
Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.