[中文]

用途:

复刻蒲公英网页「找博主 → 直播博主广场」，按电商转化力/直播表现/粉丝购买力等筛选带货博主

1. 与「笔记博主广场」的区别

两者是并列的两个选号入口，筛选维度几乎不重叠（前者看笔记种草表现，后者看直播带货表现），
但产出的博主 ID 是同一套，可以互相补全：直播侧挑出的买手可以用博主侧接口查它的笔记数据。

2. 搜索与筛选分组

分组	覆盖的筛选
`nick_name`	按博主昵称搜索（不是分组，是顶层参数）
`category`	合作品类（一级 + 二级）
`buyer`	买手天团、内容人设
`ecom`	电商转化力：场均销售额、合作品牌场均销售额、客单价
`live`	直播投入度（有直播计划、计划日期）+ 直播表现力（场均观播、在线峰值）
`fans`	粉丝购买力：粉丝量、年龄、性别、消费力
`flags`	平台推荐：积极寻求合作、邀约回复率高、可查看联系方式、商单合作过、关注关系、直播潜力高、日播买手、明星

3. 区间型字段（值写成 `{"min": x, "max": y}`）

参数路径	对应网页筛选
`fans.count`	粉丝购买力 → 粉丝量
`ecom.avg_gmv`	电商转化力 → 场均销售额（元）
`ecom.brand_avg_gmv`	电商转化力 → 合作品牌场均销售额（元）
`ecom.atv`	电商转化力 → 客单价（元）。注意上游按档位匹配，与区间有重叠的档位都会命中
`live.avg_viewer` / `live.max_online`	直播表现力 → 场均观播人数 / 在线人数峰值

4. 开关型字段（值写 `true`）

参数路径	对应网页筛选
`live.has_plan`	有直播计划（配合 `live.plan_days` 指定日期，格式 YYYYMMDD）
`flags.actively_seeking` / `flags.high_reply_rate`	积极寻求合作中 / 邀约回复率高
`flags.contact_visible` / `flags.cooperated_before`	可查看联系方式 / 商单合作过
`flags.following` / `flags.follower`	你关注 TA / TA 关注你
`flags.live_potential_high` / `flags.daily_buyer` / `flags.is_star`	直播潜力高 / 日播买手 / 明星

5. 翻页（本接口特有 `seed`）

参数	取值	说明
`page_num`	1-250	上游只放出前 5000 条 = 250 页，第 251 页起返回空数组
`page_size`	1-20	蒲公英网页固定 20
`seed`	整数	结果集种子，见下

直播博主广场的排序带随机性，不带同一个 seed 翻页会导致各页之间重复或遗漏。
用法是把上一页响应里的 seed 原样回传给下一页；首页传 0（响应里的 seed 若为 0 也原样回传即可）。
除 page_num 和 seed 外其余筛选必须保持不变。

注意 total 不是可翻数量：total 是命中总数（可能几百万），实际能翻的只有 page_total（恒为 5000）。

6. 返回

distributor_info_list[] 为命中的买手，每条含两个对象：

distributor_data_info: distributor_id(= 博主 userId) / red_id / distributor_name /
fans_num / atv 客单价档位 / avg_sale_amount 场均销售额 / avg_live_viewer_num /
max_online_people_num / distribution_live_num 场次 / content_categorys / city

distributor_extra_info: 意向品类、佣金、联系方式、等级

另有 total(命中总数) / page_total(可翻上限) / seed(翻页回传) / req_id。

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

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

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

计费:

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

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

[English]

Purpose:

Replica of PGY "Find Bloggers → Live Blogger Square"; filter live-commerce bloggers by
e-commerce conversion, live performance and fans purchasing power

1. Difference from the Note Blogger Square

They are two parallel entry points with almost no overlapping filters (note seeding vs.
live commerce), but they return the same blogger ID space, so results are cross-usable.

2. Filter Groups

Group	Covers
`nick_name`	Search by nickname (top-level param, not a group)
`category`	Cooperation categories (level 1 + 2)
`buyer`	Buyer groups, content personas
`ecom`	Average GMV, partner-brand average GMV, average transaction value
`live`	Live plans (and plan dates) + live performance (avg viewers, peak online)
`fans`	Fans count, age, gender, consumption power
`flags`	Actively seeking cooperation, high reply rate, contact visible, worked with brands, follow relations, high live potential, daily broadcaster, celebrity

3. Range Fields (value = `{"min": x, "max": y}`)

Path	Web filter
`fans.count`	Fans count
`ecom.avg_gmv` / `ecom.brand_avg_gmv`	Average GMV / partner-brand average GMV (CNY)
`ecom.atv`	Average transaction value (CNY). Upstream matches by tier, so any overlapping tier is included
`live.avg_viewer` / `live.max_online`	Average viewers / peak concurrent viewers

4. Boolean Flags (value = `true`)

Path	Web filter
`live.has_plan`	Has live plans (use with `live.plan_days`, format YYYYMMDD)
`flags.actively_seeking` / `flags.high_reply_rate`	Actively seeking / high invitation reply rate
`flags.contact_visible` / `flags.cooperated_before`	Contact visible / worked on sponsored deals
`flags.following` / `flags.follower`	You follow them / they follow you
`flags.live_potential_high` / `flags.daily_buyer` / `flags.is_star`	High live potential / daily broadcaster / celebrity

5. Paging (`seed` is specific to this endpoint)

Param	Range	Note
`page_num`	1-250	Upstream exposes only the first 5000 items; page 251+ is empty
`page_size`	1-20	Fixed at 20 on the web page
`seed`	int	Result-set seed, see below

Ranking here is randomized, so paging without a stable seed causes duplicates or gaps.
Echo back the seed from the previous response; send 0 for the first page (and echo 0
back if that is what the response contains). Keep all other filters unchanged.

total is not the pageable count: total is the match count (possibly millions), while
only page_total (always 5000) is actually reachable.

6. Return

distributor_info_list[] — matched live sellers, each with two objects:

distributor_data_info: distributor_id (= blogger userId) / red_id /
distributor_name / fans_num / atv (ATV tier) / avg_sale_amount (avg GMV) /
avg_live_viewer_num / max_online_people_num / distribution_live_num (sessions) /
content_categorys / city

distributor_extra_info: intended categories, commission, contact, level

Plus total (match count) / page_total (paging cap) / seed (echo back when paging) /
req_id.

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]

// ① 快速开始：主营女装、场均销售额 ≥10 万的买手
{"page_num": 1, "page_size": 20,
 "category": {"first": ["女装/女士精品"]},
 "ecom": {"avg_gmv": {"min": 100000}}}

// ② 有直播计划、观播人数高、且能看到联系方式的买手
{"page_num": 1, "page_size": 20,
 "live": {"has_plan": true, "avg_viewer": {"min": 10000}},
 "flags": {"contact_visible": true, "actively_seeking": true}}

// ③ 按粉丝购买力选号（女性粉丝占比高 + 高消费人群占比高）
{"page_num": 1, "page_size": 20,
 "fans": {"count": {"min": 10000, "max": 100000}, "gender": 2, "consumption": ["high"]}}

// ④ 高客单价 + 买手天团/内容人设标签（atv 按档位匹配，与区间有重叠的档位都会命中）
{"page_num": 1, "page_size": 20,
 "ecom": {"atv": {"min": 200, "max": 500}, "brand_avg_gmv": {"min": 50000}},
 "buyer": {"group_tag": ["气质简约"], "persona_tag": ["模特"]}}

// ⑤ 按昵称搜索 + 合作品类下钻到二级，只看邀约回复率高的
{"page_num": 1, "page_size": 20, "nick_name": "李",
 "category": {"first": ["女装/女士精品"], "second": ["连衣裙"]},
 "flags": {"high_reply_rate": true}}

// ⑥ 指定日期有排播的日播买手（plan_days 为 YYYYMMDD，需配合 has_plan 使用）
{"page_num": 1, "page_size": 20,
 "live": {"has_plan": true, "plan_days": ["20260901", "20260902"], "max_online": {"min": 5000}},
 "fans": {"age": 3, "consumption": ["high", "middle"]},
 "flags": {"daily_buyer": true, "live_potential_high": true}}

// ⑦ 翻页第 1 页：seed 传 0（或省略），从响应里取回本次结果集的 seed
{"page_num": 1, "page_size": 20, "seed": 0}

// ⑧ 翻页第 2 页：把上一页返回的 seed 原样带上，其余筛选必须保持不变
{"page_num": 2, "page_size": 20, "seed": 1787045123}

// 取数：buyers = resp["data"]["data"]["distributor_info_list"]；下一页要回传的 seed = resp["data"]["data"]["seed"]

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_live_blogger_list' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "page_num": 1, "page_size": 20, "seed": 0, "nick_name": "", "category": { "first": [ "string" ], "second": [ "string" ] }, "buyer": { "group_tag": [ "string" ], "persona_tag": [ "string" ] }, "ecom": { "avg_gmv": { "min": 0, "max": 0 }, "brand_avg_gmv": { "min": 0, "max": 0 }, "atv": { "min": 0, "max": 0 } }, "live": { "has_plan": true, "plan_days": [ "string" ], "avg_viewer": { "min": 0, "max": 0 }, "max_online": { "min": 0, "max": 0 } }, "fans": { "count": { "min": 0, "max": 0 }, "age": 0, "gender": 0, "consumption": [ "high" ] }, "flags": { "actively_seeking": true, "high_reply_rate": true, "contact_visible": true, "cooperated_before": true, "following": true, "follower": true, "live_potential_high": true, "daily_buyer": true, "is_star": true } }'

{ "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 }

蒲公英直播博主广场（直播带货选号）/PGY live blogger square

[中文]

用途:

1. 与「笔记博主广场」的区别

2. 搜索与筛选分组

3. 区间型字段（值写成 `{"min": x, "max": y}`）

4. 开关型字段（值写 `true`）

5. 翻页（本接口特有 `seed`）

6. 返回

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

计费:

[English]

Purpose:

1. Difference from the Note Blogger Square

2. Filter Groups

3. Range Fields (value = `{"min": x, "max": y}`)

4. Boolean Flags (value = `true`)

5. Paging (`seed` is specific to this endpoint)

6. Return

Response shape (two layers):

Billing:

[示例/Example]

Request

Responses

蒲公英直播博主广场（直播带货选号）/PGY live blogger square

[中文]#

用途:#

1. 与「笔记博主广场」的区别#

2. 搜索与筛选分组#

3. 区间型字段（值写成 {"min": x, "max": y}）#

4. 开关型字段（值写 true）#

5. 翻页（本接口特有 seed）#

6. 返回#

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

计费:#

[English]#

Purpose:#

1. Difference from the Note Blogger Square#

2. Filter Groups#

3. Range Fields (value = {"min": x, "max": y})#

4. Boolean Flags (value = true)#

5. Paging (seed is specific to this endpoint)#

6. Return#

Response shape (two layers):#

Billing:#

[示例/Example]#

Request

Responses

[中文]

用途:

1. 与「笔记博主广场」的区别

2. 搜索与筛选分组

3. 区间型字段（值写成 `{"min": x, "max": y}`）

4. 开关型字段（值写 `true`）

5. 翻页（本接口特有 `seed`）

6. 返回

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

计费:

[English]

Purpose:

1. Difference from the Note Blogger Square

2. Filter Groups

3. Range Fields (value = `{"min": x, "max": y}`)

4. Boolean Flags (value = `true`)

5. Paging (`seed` is specific to this endpoint)

6. Return

Response shape (two layers):

Billing:

[示例/Example]