[中文]

用途:

获取博主的逐日趋势与区间汇总，用于绘制表现趋势图

对应博主主页「笔记数据 → 数据表现 → 核心指标趋势」

请求体参数:

user_id: 必填，博主用户ID

business: 笔记口径，0=日常笔记(默认) 1=合作笔记

note_type: 笔记类型，3=图文+视频(默认) 1=图文 2=视频
注意: 与 /get_blogger_notes 的同名参数取值不同（那个是 4=全部 3=合作笔记）

date_type: 时间范围，1=近30日(默认) 2=近90日

advertise_switch: 流量类型，1=全部(含合作，默认) 0=仅自然流量

dailyData[]: 逐日趋势数据点

sumData: 区间汇总（曝光/阅读/互动/CPM/CPE 等）

响应结构（取数要剥两层）:

resp["data"] 是蒲公英原样信封（含 code/msg/success），业务数据还在它里面一层

正确取法：data = resp["data"]["data"]；下面「返回」列的字段都在这一层下

计费:

HTTP 200 → 计费。包含「查无结果」（data 为 null，如 ID 不存在或筛选无命中）——
请求已送达蒲公英，同样扣费，不要因为拿不到数据就重试

HTTP 400 → 不计费（参数格式非法，或上游资源不足/异常）

[English]

Purpose:

Daily trend and period summary of a blogger, for plotting performance charts

Request Body Parameters:

user_id: required, blogger user ID

business: 0=organic (default), 1=sponsored

note_type: 3=image-text+video (default), 1=image-text, 2=video
Warning: differs from /get_blogger_notes, where 4=all and 3=sponsored

date_type: 1=last 30 days (default), 2=last 90 days

advertise_switch: 1=all traffic (default), 0=organic only

Return:

dailyData[]: daily data points

sumData: period aggregates (impressions / reads / engagements / CPM / CPE)

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]

// ① 默认：日常笔记 · 近 30 日趋势
{"user_id": "5c668b3e0000000012021605"}

// ② 近 90 日
{"user_id": "5c668b3e0000000012021605", "date_type": 2}

// ③ 合作笔记口径 · 仅自然流量
{"user_id": "5c668b3e0000000012021605", "business": 1, "advertise_switch": 0}

// ④ 只看视频 · 近 90 日 · 合作笔记
{"user_id": "5c668b3e0000000012021605", "business": 1, "note_type": 2, "date_type": 2}

dailyData[] 可直接画趋势图，sumData 是同区间的汇总值。
逐日点数随 date_type 变化（近 30 日约 30 个点）。

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

curl --location 'https://api.tikhub.io/api/v1/xiaohongshu/pgy/get_blogger_core_data' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "user_id": "5c668b3e0000000012021605", "business": 0, "note_type": 3, "date_type": 1, "advertise_switch": 1 }'

{ "code": 200, "request_id": "string", "message": "Request successful. This request will incur a charge.", "message_zh": "请求成功，本次请求将被计费。", "support": "Discord: https://discord.gg/aMEAS8Xsvz", "time": "string", "time_stamp": 0, "time_zone": "America/Los_Angeles", "docs": "string", "cache_message": "string", "cache_message_zh": "string", "cache_url": "string", "router": "", "params": {}, "data": null }

获取蒲公英博主核心数据/Get PGY blogger core data trend

[中文]

用途:

请求体参数:

返回:

响应结构（取数要剥两层）:

计费:

[English]

Purpose:

Request Body Parameters:

Return:

Response shape (two layers):

Billing:

[示例/Example]

Request

Responses

获取蒲公英博主核心数据/Get PGY blogger core data trend

[中文]#

用途:#

请求体参数:#

返回:#

响应结构（取数要剥两层）:#

计费:#

[English]#

Purpose:#

Request Body Parameters:#

Return:#

Response shape (two layers):#

Billing:#

[示例/Example]#

Request

Responses

[中文]

用途:

请求体参数:

返回:

响应结构（取数要剥两层）:

计费:

[English]

Purpose:

Request Body Parameters:

Return:

Response shape (two layers):

Billing:

[示例/Example]