RedNote Pugongying (Dandelion) Data API: Blogger Selection, Fan Profiles & Conversion

For RedNote (Xiaohongshu) influencer marketing, creator selection and competitor analysis, the most valuable data lives inside Pugongying (Dandelion) — RedNote's official creator-marketing platform: real fan profiles, note conversion rates, quotes, engagement medians, follower growth… data you can't get from ordinary crawler APIs. Rnote API's new Pugongying data endpoints wrap these into standard REST APIs — pay per call, charged only on success.

What you can get

A set of endpoints spanning "note → blogger → selection":

Note detail POST /api/v2/pgy/note/detail — content, image/video media, impressions/reads/likes/collects/comments.
Blogger detail POST /api/v2/pgy/blogger/detail — name, RedNote ID, region, tags, followers, likes & collects, image/video collaboration quotes, collaboration status.
Blogger note list POST /api/v2/pgy/blogger/notes — paginated notes with reads/likes/collects, video flag, sponsored flag; filter by type and sort.
Note conversion / performance POST /api/v2/pgy/blogger/notes-rate — impression/read/engagement medians, engagement rate, video completion rate, 100-like / 1000-like ratios, content-format mix, and peer "beyond rates".
Core data POST /api/v2/pgy/blogger/core-data — daily trend + period summary (impressions/reads/engagement/CPM/CPE).
Data overview POST /api/v2/pgy/blogger/data-summary — cost & quote estimates (CPM/CPUV/read cost), content-format mix, monthly fan growth, collaboration verticals.
Fans summary / profile / growth — follower counts and active/engaged/paying fans, age-gender-region-interest-device profile, daily growth curve.
Blogger list (selection) POST /api/v2/pgy/blogger/list — filter candidate bloggers by brand and follower range for bulk shortlisting.

Typical use cases

Influencer selection — Filter by brand & followers via the list, then due-diligence with detail + conversion + fan profile to pick the best fit.
Audience matching — Use fans' age/gender/region/interest distribution to check whether a creator's audience matches your target.
Quote & ROI evaluation — Compare image/video quotes against read cost and engagement medians to judge budget efficiency.
Competitor & vertical analysis — Pull competitors' partner bloggers' core data and trends to review strategy.

How to use

Sign up free and create an API Key (new accounts get crawler + Pugongying access by default).
Call /api/v2/pgy/* with X-API-Key; the body only needs business params (e.g. user_id, note_id, pagination, note type).
Try it live in the Swagger API docs — each endpoint documents its parameter values and response fields.

Billing

Pugongying endpoints are pay-per-call, charged only on a successful business result; failures (rate limits, bad params) are not billed. See the pricing page.

Endpoints added since

This post originally covered the note → creator → selection path. Several groups have been added since, extending it back into deciding what to say before deciding who says it:

Content Square POST /api/v2/pgy/content/square — the platform-side content distribution for a category: what everyone is publishing, not just what matches your term.
Keyword analytics keyword/stat / keyword/daily / keyword/related — overall performance, day-by-day trend, and related-term expansion. Start with keyword/daily: bet on terms that are rising, not terms that are already high.
Live Blogger Square POST /api/v2/pgy/live-blogger/list — for live-commerce selection. Note this is a different pool from blogger/list; accounts filtered from the latter may not stream at all.
Similar creators POST /api/v2/pgy/blogger/similar — start from a partner that already performed and find the next one like them, far faster than re-screening a category.
Note comments / components note/comments / note/components — real feedback under a commercial note and the components attached to it.
Cross-domain note cases POST /api/v2/pgy/blogger/notes_v2 — the original blogger/notes returns empty for cross-domain creators; use notes_v2 there. The two have different response shapes and are not interchangeable.

Paging and per-page limits

Per-page limits follow the values the Pugongying web app actually uses and differ per endpoint — asking for more returns no more, it just truncates. Limits and paging are in the docs; two minutes there before you write the loop saves a round of "why did I only get this many".

The full selection chain

Strung together, pre-campaign selection looks roughly like this:

1. keyword/related + keyword/daily   direction: which terms are rising
2. content/square                    which formats are working in those directions
3. blogger/list                      candidate pool by category and follower band
4. fans-profile                      hard-filter on city/age (removes most of the pool)
5. notes-rate                        drop "right audience, no reach" on engagement rate
6. fans-history                      due-diligence the survivors on growth shape
7. blogger/detail                    only now pull rates; compute cost per effective reach
8. blogger/similar                   after a partnership works, find the next batch

The order matters: rates come last. That endpoint is typically the most expensive of the set, and using it to screen is pure waste. Shrink the pool with profile and engagement data first, then price what survives.

Steps 1–3 are covered in Content Square and keyword analytics; steps 4–6 in reading Pugongying audience profiles.

FAQ

Q: How is this different from the regular crawler APIs? A: Regular APIs return public note/user/search data; Pugongying endpoints return commercial blogger data from the official marketing platform (quotes, conversion, fan profiles) — the data that drives campaign decisions.

Q: Do I need my own accounts / cookies? A: No. The service handles data collection with automatic scheduling, rate-limiting and rotation — you just call with an API Key.

Q: Is it stable? A: It runs with built-in health-based scheduling, rate-limiting and cooldowns, isolated from the other crawler services.