datawebotXiaohongshu note, product and shop data
Separate Xiaohongshu notes, product links, livestream commerce and merchant-authorized catalog records with clear source and account scope.
Keep Xiaohongshu notes, products and shop accounts distinct
Xiaohongshu merchant materials describe content, shops and live commerce as connected activities, but their records have different owners and grains. Preserve the source identity and the relationship between records instead of merging them into a single product row.
Scroll to compare →
| Record | Retain when shown or authorized | Do not substitute |
|---|---|---|
| Note (笔记) | Source URL or visible ID, public author label, displayed text/media format, publication context and visible topic/location labels. | A note is not the canonical shop item or a verified product review. |
| Shop product (商品) | Shop/item key and title from the linked destination or authorized merchant catalog; preserve variation keys as returned. | A repeated creator name or image as proof of item identity. |
| Creator/account | Public display name and source context when visible; account key only in an authorized record. | Private profile, contact or login data in a public product record. |
| Relationship | Note-to-product destination, live-to-product association or campaign reference when the source exposes it. | A link as proof of ownership, stock, endorsement or transaction. |
Treat a note or livestream product link as a relationship
Xiaohongshu's merchant learning and collaboration materials connect notes, products and livestreams. Keep the content item and the linked shop destination as separate records so a later link change or product change does not rewrite the original content observation.
Scroll to compare →
| Content-commerce link | Useful observation fields | Boundary |
|---|---|---|
| Shoppable note | Note URL/visible ID, publisher label, displayed product or shop link, linked item title and observation time. | A product attachment does not confirm that the item is in stock or that the note creator is the seller. |
| Shop item reference | Destination URL and shop/item identity when exposed; retain the note that presented it. | Do not infer a platform-wide catalog relationship from a title or thumbnail match. |
| Livestream product connection | Visible live/session context and attached shop/item destination when displayed. | A live product link is not the livestream's private order or sales record. |
| Visible interaction | Publicly shown likes/comments or other source-labeled count with the observation time. | Engagement is not orders, conversion or audience identity. |
Keep catalog and inventory APIs within an authorized shop
The official Open Platform separates merchant API families and assigns API/message permissions by developer application category. Those tools support authorized store operations; they do not establish anonymous access to every shop, public note-search data or competitors' inventory.
Scroll to compare →
| Official API scope | Documented role | Record boundary |
|---|---|---|
| Product API | Merchant product management and catalog operations. | Use the shop's returned item and variation keys; do not identify an item by content text alone. |
| Inventory API | Merchant inventory operations in supported app categories. | Keep the authorized shop, item/variant, state and observation time together. |
| Order and after-sales APIs | Order and after-sales workflows where the app category has those permissions. | Keep buyer/order details inside the authorized business workflow; do not republish them as public listing data. |
| Application category and authorization | Different app types receive different API and message scopes; the developer docs describe app credentials and token authorization. | Do not present merchant-only APIs as a general public content or product feed. |
Keep Pugongying creator reports tied to the campaign account
Official Pugongying materials describe brand and creator collaborations that link note and livestream activity and provide post-campaign reporting. Those report views are account and campaign context, not fields visible on an ordinary public note.
Scroll to compare →
| Campaign record | Preserve in an authorized report | Do not expose as public product data |
|---|---|---|
| Collaboration | Brand/creator relationship, collaboration order, selected goods and whether the agreed deliverable is a note, live session or both. | Private negotiated rates, creator contact information or order terms. |
| Published content | The public note/live URLs linked to the campaign and the report period. | The campaign relationship as proof that other posts are sponsored or affiliated. |
| Post-campaign performance | The report's own note/live performance and conversion measures, with source label and period. | A public engagement count as a campaign sale or conversion metric. |
| Audience and product scope | Authorized SPU and analysis-period selection where the Pugongying report exposes it. | Individual audience profiles, buyer identity, messages or raw account-level event data. |
Content reviewed 2026-10-07.