Xiaohongshu-PGY-API
获取蒲公英博主数据概览/Get PGY blogger data summary
Changed on[中文]
用途:
- 获取博主账号维度的数据概览汇总
请求体参数:
- user_id: 必填,博主用户ID
- business: 笔记口径,0=日常笔记(默认) 1=合作笔记
返回:
- 成本/报价预估: estimatePictureCpm / estimateVideoCpm / pictureReadCost 等
- 服务表现: 近 7 天活跃天数、邀约 48 小时回复率
- 成长表现: 粉丝量变化幅度及其同行百分位
响应结构(取数要剥两层):
- resp["data"] 是蒲公英原样信封(含 code/msg/success),业务数据还在它里面一层
- 正确取法:data = resp["data"]["data"];下面「返回」列的字段都在这一层下
计费:
- HTTP 200 → 计费。包含「查无结果」(data 为 null,如 ID 不存在或筛选无命中)—— 请求已送达蒲公英,同样扣费,不要因为拿不到数据就重试
- HTTP 400 → 不计费(参数格式非法,或上游资源不足/异常)
[English]
Purpose:
- Account-level data summary of a blogger
Request Body Parameters:
- user_id: required, blogger user ID
- business: 0=organic (default), 1=sponsored
Return:
- Cost/quote estimates: estimatePictureCpm / estimateVideoCpm / pictureReadCost
- Service metrics: active days in last 7d, 48h invitation reply rate
- Growth: fans change rate and percentile vs peers
Response shape (two layers):
- resp["data"] is PGY's raw envelope (with code/msg/success); the payload is one level deeper
- Correct access: data = resp["data"]["data"] — every field listed under "Return" lives here
Billing:
- HTTP 200 → charged, including "no result" (data is null, e.g. ID not found or filters matched nothing): the request did reach PGY, so retrying on empty data just burns quota
- HTTP 400 → not charged (malformed params, or upstream unavailable/error)
[示例/Example]
// ① 日常笔记口径
{"user_id": "5c668b3e0000000012021605"}
// ② 合作笔记口径(按商单价格评估性价比时用这个)
{"user_id": "5c668b3e0000000012021605", "business": 1}
两种口径的成本类指标不同 —— 实测同一博主日常图文 CPM ≈11、合作口径 ≈19。 想评估「按商单价格算的性价比」请传 business=1。
The two modes yield different cost metrics; pass business=1 to evaluate sponsored-price ROI.
post/api/v1/xiaohongshu/pgy/get_blogger_data_summary
Request
- Base URLhttps://api.tikhub.io (the document declares no server; this is the origin it was published from)
- AuthHTTP bearer
Request body
Example request
{
"user_id": "5c668b3e0000000012021605"
}Response
Successful Response
Changes
- info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status
- info
- info
endpoint added
- info