Xiaohongshu Account Content List
Collect public Xiaohongshu account content with account identifiers, titles, and collection timestamps
Original · en-USZur Übersetzung
Übersicht
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.
Anwendungsbereich & Grenzen
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.
- Geeignet für
- 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
- Nicht verwenden für
- When you need private, deleted, restricted, or login-only content
- When you need an instant single-record lookup rather than a collected list
Fehlerbehandlung
Vom Autor deklariertes Fehler- und Wiederholungsverhalten. Wir empfehlen, es bei der Integration in Ihren System-Prompt aufzunehmen.
- 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
Eingabe
Parameter, die zum Aufruf dieser App erforderlich sind, generiert aus dem input.schema in der manifest.json.
| Feld | Fachlicher Name | Typ | Erforderlich | Standard | Enum / Einschränkungen | Beispiel | Beschreibung |
|---|---|---|---|---|---|---|---|
| account_id | Xiaohongshu account ID | string | Ja | — | — | 6366a311000000001f01fd6c | The Xiaohongshu account ID whose public content should be collected. Enter 1 to 512 characters. |
| crawl_num | Expected content count | integer | Ja | — | 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. |
Ausgabe
Feldstruktur eines einzelnen Datensatzes, generiert aus dem output.schema in der manifest.json.
| Feld | Fachlicher Name | Typ | Beispiel | Beschreibung |
|---|---|---|---|---|
| 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. |
Datensatz-Schema
Die Ausgabe wird Datensatz für Datensatz zurückgegeben. 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
}Integration
Diese App kann über MCP, API, SDK oder Dateiexport integriert werden — alle Kanäle teilen sich dieselben Fähigkeiten und Preise. Jede Anfrage authentifiziert sich über den Authorization: Bearer-Header mit einem API Key (langlebig, in der Data Hub Konsole erstellt); MCP-Clients können sich zusätzlich per OAuth ohne Key anmelden. Weitere Optionen wie CLI und Skill sind in Vorbereitung.
Über das MCP (Model Context Protocol) können Sie diese App direkt aus KI-Clients wie Claude und Cursor aufrufen. Wählen Sie Ihren Client und den Authentifizierungsmodus und kopieren Sie dann die Konfiguration unten.
Client-Konfiguration
Ersetzen Sie den Wert nach Bearer durch Ihren langlebigen API Key. Funktioniert in jedem Client, in CI und in Headless-Umgebungen.
{
"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>" }
}
}
}Lassen Sie die KI die Einrichtung übernehmen
Sie möchten Konfigurationen nicht von Hand bearbeiten? Kopieren Sie den Installations-Prompt und fügen Sie ihn in einen beliebigen KI-Client ein — er schließt die Einrichtung auf seine eigene Weise ab. (Der Prompt weist die KI an, Ihren API Key bei Ihnen zu erfragen, damit Zugangsdaten nie im Chatverlauf oder in geteilten Konfigurationen landen.)
detail.access.mcp.composeHint
Preise
Berechnet nach der Anzahl der erfolgreich zurückgegebenen Datensätze. Fehlgeschlagene Läufe werden nicht berechnet. Abgerechnet in Einheiten von 20 Datensatz; jede angefangene Einheit wird auf 20 Datensatz aufgerundet.
Wird pro übermitteltem Lauf einmal berechnet, unabhängig davon, wie viele Datensätze zurückgegeben werden.
Mehrere Abrechnungsereignisse werden unabhängig voneinander kumuliert. Details siehe jeweilige Position. Fehlgeschlagene Läufe werden nicht berechnet.
Credits ansehenJetzt ausprobieren
Füllen Sie die Parameter aus und starten Sie — die Ergebnisse stammen aus einem echten Aufruf.