DataNavoAPI / ANSWERS / REDNOTE

How do note traffic sources differ from public note fields?

How do note traffic sources differ from public note fields? Follow concrete contracts, examples and reviewable steps using Xiaohongshu (RedNote).

LOCAL SIMULATIONAll displayed records are fictional fixtures. Live APIs, payments and external email are disabled.中文版 ↗
01

Answer

Start by inspecting the contracts and local samples for Xiaohongshu PGY note metrics. Establish the input for xiaohongshu.pgy.notes.get, then check whether its pgy_note object contains the fields your task needs.

Align the metric name, denominator, observation window and capture time first. Indices, reads, impressions, plays, engagement and cost are different measurements. A missing value means unavailable, not zero; likes cannot substitute for reads.

02

Relevant contracts

CapabilityObjectShapePagination
xiaohongshu.pgy.notes.getPgy note metricsitemNo cursor
03

Input contract

Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.

  • Only send fields defined for this method; unknown fields are rejected before execution.
MethodFieldTypeRequirementMeaningEnum or boundExample
GETidstringRequiredNote ID, 24 hexadecimal characters: the part after explore/ in a Xiaohongshu note link, or an id the PGY creator notes endpoint returns—"6a20edfa0000000021020951"
GETviewstringOptional / conditionalHow much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`).["compact","standard","full"]—
GETfieldsarrayOptional / conditionalReturn only these fields of each item, by path (`author.name`).maxItems: 64—
04

Complete one verification

Run one local fixture for a listed capability and inspect the object structure. Then filter, classify or export according to the question. A local sample cannot replace evidence for a real-platform conclusion.

json
{
  "capability": "xiaohongshu.pgy.notes.get",
  "method": "GET",
  "params": {
    "id": "6a20edfa0000000021020951"
  }
}
TRY THE CONTRACT

Clear inputs. Inspectable output.

Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.

Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.

Download contract example (no execution) ↗

For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗