DataNavoAPI / ANSWERS

Which measurement differences matter between Pgy and Xingtu?

Which measurement differences matter between Pgy and Xingtu? Follow concrete contracts, examples and reviewable steps using Xiaohongshu (RedNote), Douyin.

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 creator metrics, Douyin Xingtu creator metrics. Establish the input for xiaohongshu.pgy.creators.metrics, then check whether its pgy_creator_metrics object contains the fields your task needs.

Document the input scope, sampling rule and intended use, and preserve request IDs and missing-field markers. An API supplies the contracted sample; interpretation still requires checks of context and representativeness.

02

Relevant contracts

CapabilityObjectShapePagination
xiaohongshu.pgy.creators.metricsPgy creator metricsitemNo cursor
douyin.xingtu.creators.metricsXingtu creator 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
GETidstringRequiredPGY creator ID, 24 hexadecimal characters; take it from the PGY creator search—"5c0017ef6b58b740c92463fb"
GETwindowstringOptional / conditionalThe period: the last 30 or the last 90 days["30d","90d"]—
GETtabstringOptional / conditionalWhose figures: everyday for the creator's everyday notes, sponsored for the sponsored ones; everyday by default, as the two tabs of the creator's PGY page["everyday","sponsored"]—
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.creators.metrics",
  "method": "GET",
  "params": {
    "id": "5c0017ef6b58b740c92463fb"
  }
}
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 ↗