Xiaohongshu vs Pugongying: Content Data or Campaign Data

The short answer

Xiaohongshu and Xiaohongshu Pugongying are not the same data surface. Xiaohongshu is the consumer content platform, so it is the right place to work with public notes, comments, user profiles, search results, and share-link resolution. Pugongying is the creator marketplace and campaign collaboration platform, so it is the right place for creator marketing, audience insights, note performance, campaign review, and commercial collaboration data.

If you need the read count or view count of a note, start with Pugongying APIs. The public Xiaohongshu app is built for ordinary users, and ordinary users usually cannot see note read count on the public note detail page. That means you should not model read count as a stable field from the normal Xiaohongshu note detail endpoint.

The practical difference

Think of Xiaohongshu as the content platform. Users search, browse, publish, comment, like, and save notes. For data workflows, it is useful for content discovery, social listening, account monitoring, comment analysis, and note archiving.

Think of Pugongying as the creator marketing platform. Brands, agencies, and creators use it for commercial collaboration, creator selection, in-campaign monitoring, and post-campaign review. For data workflows, it is useful for influencer vetting, follower distribution, note performance, pricing signals, cost effectiveness, and campaign reporting.

Just One API keeps the same boundary in its site copy: Xiaohongshu is for post content and creator data, while Xiaohongshu Pugongying is for brand collaboration data.

Why read count belongs to Pugongying

A common product question is: can I get the read count for this note? The important distinction is whether the field is visible in the ordinary consumer experience or belongs to creator and campaign analytics.

When an ordinary user opens a Xiaohongshu note, they can usually see the content, author, interaction entry points, and some public engagement signals. They do not get the same backend-style read or view count that a campaign or creator analytics workflow needs. Normal Xiaohongshu APIs are therefore better for content and public interaction data.

Pugongying has a different purpose. It supports commercial collaboration and campaign review. In the Just One API documentation, the Pugongying note detail endpoint is described as a way to retrieve media and engagement signals, and its highlight notes that the endpoint can retrieve view counts, while engagement metrics may be unavailable for some posts. In practice, read or view count should be modeled through the Pugongying data path, with null or unavailable values handled explicitly.

When to use Xiaohongshu APIs

Use Xiaohongshu APIs when the job is about public content and community data.

• Search notes by keyword for topic discovery, trend monitoring, and competitor research.
• Retrieve note details for title, body, images, videos, and public engagement signals.
• Retrieve note comments and replies for feedback analysis, sentiment analysis, and issue collection.
• Retrieve user profiles and published notes for account monitoring and creator pre-screening.
• Resolve share links so you can extract a note ID before calling detail or comment endpoints.

Common entry points include Xiaohongshu note search, note details, note comments, user profile, and share-link resolution. For endpoint versions and parameter details, open the Xiaohongshu API docs.

Normal Xiaohongshu note detail data is suitable for content and public engagement signals. It should not be treated as the stable source for read count, because read count is not normally visible to ordinary users in the public app surface.

When to use Pugongying APIs

Use Pugongying APIs when the job is about creator marketing, collaboration, and campaign performance.

• Review creator profiles, collaboration signals, and marketing-oriented creator data.
• Analyze follower profiles, follower growth, audience distribution, and content tags.
• Review note performance metrics for content efficiency and creator benchmarking.
• Inspect cost effectiveness, pricing signals, and campaign review metrics.
• Retrieve Pugongying note details when you need performance data such as read or view count that is not exposed in the public consumer surface.

Common entry points include Pugongying creator profile, follower distribution, follower summary, note performance metrics, creator search, content square notes, and Pugongying note details. For endpoint versions and parameter details, open the Xiaohongshu Pugongying API docs.

Pugongying note detail data is the better fit for read count, view count, and campaign performance fields. If your product schema includes these metrics, start with Pugongying and make sure unavailable metrics are handled cleanly.

A simple selection workflow

First decide whether the task is a content task or a campaign task. If you need notes, comments, public author pages, and public discovery, use Xiaohongshu. If you need creator commercial value, audience profiles, note performance, or read count, use Pugongying.

Next, ask whether the field is visible to ordinary users. If ordinary users cannot see the backend-style metric in the public app, do not expect the normal Xiaohongshu endpoint to return it reliably. Read count is the typical example: it belongs closer to creator analytics and campaign review, so Pugongying is the better data path.

Finally, treat unavailable values as a normal state. Pugongying covers more marketing data, but the documentation also notes that engagement metrics may be unavailable for some posts. Your integration should support null values, delayed retries, or alternative evaluation metrics.

Prompts for MCP or an API assistant

If you use JustOneAPI MCP Server, ask in normal business language and let the assistant find the endpoint.

• I need Xiaohongshu note details, but I do not need read count. Which endpoint should I use?
• I need the read count or view count for a Xiaohongshu note. Find the related Pugongying endpoint and explain the required parameters.
• I need to evaluate Pugongying creators for a campaign, including follower profiles, note performance, and cost effectiveness.
• I have a Xiaohongshu note ID. Help me decide whether I should use the normal Xiaohongshu API or a Pugongying API.

Next steps

If you are building Xiaohongshu content monitoring, start with note search, note details, and comments in the Xiaohongshu API docs. If you are building creator marketing, campaign review, or read and view count workflows, choose the right endpoint from the Xiaohongshu Pugongying API docs.

Before calling an API, open JustOneAPI Dashboard to get your token. Real tokens are sensitive, so do not put them in public repositories, public screenshots, or messages to untrusted recipients.