[中文]

用途:

获取 /get_blogger_list 里那些树形筛选的可选值，是找博主的配套字典接口

这些选项由平台维护、会随运营变动，不要写死在代码里；结果基本不变，建议客户端缓存后复用

请求体参数:

无

industryTags → 网页「行业」（taxonomy1Tag 一级 + taxonomy2Tags 二级），
填进 /get_blogger_list 的 coop.industry / flags.industry_first
—— 这是「行业」，不是「博主类目」；博主类目 blogger.content_tag 不在本字典里，
直接填网页类目名（美妆/护肤/母婴/时尚…）

personalTagsV2 → 网页「博主人设」（家庭身份 / 职业身份 / 特色背景 → 分组 → 叶子标签）

featureTags → 网页「擅长内容」（一级 + 二级）

contentTheme → 网页「内容题材」

audience20 → 网页「二十大人群」

automotiveIndustryTag → 网页「行业特色画像」

consumerBehavior → 网页「预估消费行为」（部分账号为 null）

market → 网页「营销目标」

activities → 网页「平台推荐 → 热门活动」，每项的 code 即 flags.activity_codes 的取值

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

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

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

计费:

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

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

[English]

Purpose:

Fetch selectable values for the tree-style filters used by /get_blogger_list

These are maintained by the platform and change over time — do not hardcode them;
the result is fairly stable, so caching on the client side is recommended

Request Body Parameters:

None

Return:

industryTags → industry (taxonomy1Tag L1 + taxonomy2Tags L2), feeds
coop.industry / flags.industry_first of /get_blogger_list
— this is "industry", NOT "blogger category"; blogger category
(blogger.content_tag) is not in this dictionary — pass the site's category
name directly (美妆/护肤/母婴/时尚…)

personalTagsV2 → blogger personas (family / occupation / background → group → leaf)

featureTags → content expertise (level 1 + 2)

contentTheme → content themes

audience20 → top-20 crowd segments

automotiveIndustryTag → industry-specific portraits

consumerBehavior → estimated consumption behavior (may be null for some accounts)

market → marketing goals

activities → campaigns; each code is a valid value for flags.activity_codes

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]

// 取全部字典（首次接入时跑一次，把结果缓存起来）
{}

字典变化很慢，建议本地缓存复用，不必每次筛选前都调。

需要先查本接口才能填的筛选：博主类目（contentTags，含二级如美妆 → 唇妆/眼妆）、
笔记场景（contentScenes）、预估消费行为（consumerBehavior）、
博主地域（areas，到区县）、粉丝地域（fansAreas，只到市）。
其余多数筛选是固定枚举，照 /get_blogger_list 的文档直接填即可。

Cache the result — it rarely changes. Dictionary-backed filters: blogger category,
note scene, consumption behavior, blogger/fans location.

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

{ "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 filter options

[中文]

用途:

请求体参数:

返回:

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

计费:

[English]

Purpose:

Request Body Parameters:

Return:

Response shape (two layers):

Billing:

[示例/Example]

Request

Responses

获取蒲公英找博主筛选项字典/Get PGY blogger filter options

[中文]#

用途:#

请求体参数:#

返回:#

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

计费:#

[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]