Pugongying Content Square and Keyword Analytics: Decide What to Say Before Who Says It
Creator selection answers who. Content Square and keyword analytics answer the question that comes before it: what is actually running in this space right now, and what are people searching for.
Content Square: what's running
POST /api/v2/pgy/content/square pulls the platform-side content pool filtered by category, time window and note type. The difference from ordinary search: search returns notes matching a term, while Content Square returns the distribution of content across a category — what everyone is publishing, not just what matches your term.
Run it once at the start of content planning: which directions this category clusters around this week, whether image or video dominates, and what engagement band the top notes sit in. That band is the realistic expectation for your campaign — a far better reference than platform-wide viral outliers.
Keyword analytics: three endpoints, three angles
| Endpoint | What it answers |
|---|---|
POST /api/v2/pgy/keyword/stat |
Overall performance of this term |
POST /api/v2/pgy/keyword/daily |
Day-by-day trend for this term |
POST /api/v2/pgy/keyword/related |
Terms related to this one |
Start with keyword/daily. High absolute volume often just means the term is broad; the upward trend is the signal you can bet on. Content has lag — the topic you choose today publishes in two weeks — so bet on "rising", not "already high".
Use keyword/related to expand: start from one term you're sure about, pull related terms, then run each through keyword/daily. You quickly get a set of "related and rising" long-tail terms, which are far less contested than head terms and much friendlier to a young account.
Blogger Square and Live Blogger Square
POST /api/v2/pgy/blogger/list is the note-creator pool; POST /api/v2/pgy/live-blogger/list is the live-streaming pool — they are different pools. For live commerce selection use the latter; accounts filtered from the former may not stream at all.
POST /api/v2/pgy/blogger/similar finds creators similar to one you already know is good, which is much faster than re-screening a whole category. Taking a partner that already performed and asking for "the next one like this" is one of the highest-leverage steps in campaign planning.
Putting it together
1. keyword/related expand a seed term into ~30 related terms
2. keyword/daily check each trend, keep the 8 clearly rising
3. content/square see which formats are working in those directions
4. blogger/list shortlist creators by category
5. blogger/similar find lookalikes for creators that already worked
The first three steps decide what to say; the last two decide who says it. Reverse the order and you'll happily book an excellent creator to talk about something nobody is searching for.
A note on paging
Per-page limits follow the values the Pugongying web app actually uses, and they differ per endpoint — asking for more will not return more. Limits and paging are documented in the docs.
Get started
Sign up free and call them directly — only successful calls are billed. For the selection half, see reading Pugongying audience profiles.
Related articles
- Reading Pugongying Audience Profiles: From Follower Counts to Real Due Diligence City concentration, age overlap, gender extremes and growth-curve shape — how to read the four Pugongying audience endpoints, plus a screening order that cuts call volume.
- Usage Doesn't Add Up? Split Billing by Date and by Endpoint Locate the anomalous day, find the expensive call pattern, export and reconcile against your own logs — plus three ten-minute checks that nearly always find something.
- Build a RedNote Competitor Dashboard from Scratch: One Table, One Cron Job Questions before fields; a three-layer collect/store/present design; snapshots instead of current values; three metrics that earn their place; and what 50 calls a day costs.
- Batch Crawls That Don't Die Halfway: Error Classes, Backoff and Resumability Split failures into retryable, not-retryable and stop-the-job; back off with a cap; persist progress and flush it; then patch with a second pass. Copyable Python included.
About the Rnote Xiaohongshu API
Skip building a RedNote scraper: one API key gets you notes, comments, users, search, products and Pugongying creator data. Pay per call, charged only for successful requests.