[中文]

用途:

• 获取单个博主的详细资料，对应蒲公英博主主页顶部资料区
• 结果已内嵌大量指标，通常不必再逐个调其它博主数据接口

请求体参数:

• user_id: 博主用户ID，如 "5c668b3e0000000012021605"

返回:

• 博主资料: userId / name / redId(小红书号) / headPhoto / location(地区) / personalTags(标签)
• 商业信息: 图文与视频报价、合作状态、所属机构(MCN)
• 标签: contentTags(内容类目) / featureTags(内容特征)
• 数据: 粉丝数、各项中位数、近 30 天曝光等

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

• resp["data"] 是蒲公英原样信封（含 code/msg/success），业务数据还在它里面一层
• 正确取法：data = resp["data"]["data"]；下面「返回」列的字段都在这一层下

计费:

• HTTP 200 → 计费。包含「查无结果」（data 为 null，如 ID 不存在或筛选无命中）—— 请求已送达蒲公英，同样扣费，不要因为拿不到数据就重试
• HTTP 400 → 不计费（参数格式非法，或上游资源不足/异常）

[English]

Purpose:

• Get full profile of a single blogger (PGY blogger homepage header)
• The response already embeds many metrics, so other blogger endpoints are often unnecessary

Request Body Parameters:

• user_id: Blogger user ID, e.g. "5c668b3e0000000012021605"

Return:

• Profile: userId / name / redId / headPhoto / location / personalTags
• Commercial: image-text & video quotes, cooperation status, MCN agency
• Tags: contentTags / featureTags
• Metrics: fans count, medians, last-30d impressions

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 从 /get_blogger_list 结果的 kols[].userId 取，或从蒲公英博主主页 URL 里截。 想要更细的数据分别用：/get_blogger_data_summary（成本与报价预估）、 /get_blogger_notes_rate（笔记表现）、/get_blogger_fans_profile（粉丝画像）。

Get user_id from /get_blogger_list → kols[].userId, or from the blogger's PGY page URL.

{
  "user_id": "5c668b3e0000000012021605"
}