---
title: "获取蒲公英博主粉丝增长历史/Get PGY blogger fans growth history"
method: POST
path: "/api/v1/xiaohongshu/pgy/get_blogger_fans_history"
tags: ["Xiaohongshu-PGY-API"]
---

# 获取蒲公英博主粉丝增长历史/Get PGY blogger fans growth history

`POST /api/v1/xiaohongshu/pgy/get_blogger_fans_history`

## Request

- Base URL: `https://api.tikhub.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.tikhub.io/api/v1/xiaohongshu/pgy/get_blogger_fans_history`
- Auth: HTTP bearer

# [中文]
### 用途:
- 获取博主粉丝随时间的变化曲线，对应博主主页「粉丝分析 → 粉丝趋势」
### 请求体参数:
- user_id: **必填**，博主用户ID
- increase_type: 曲线口径，1=**粉丝总量**(默认，累计数) 2=**粉丝增量**(每日新增)
- date_type: 时间范围，1=近30日(默认) 2=近60日
### 返回:
- list[]: 逐日数据点（当日值与日期）
- fansNumInc: 区间净增
- fansNumIncRate: 区间增长率
### 提示:
- 两个参数的默认值都与蒲公英网页一致（粉丝总量 + 近30日）
- 要看每日新增曲线请传 increase_type=2

### 响应结构（取数要剥两层）:
- `resp["data"]` 是蒲公英原样信封（含 `code`/`msg`/`success`），业务数据还在它里面一层
- 正确取法：`data = resp["data"]["data"]`；下面「返回」列的字段都在这一层下
### 计费:
- HTTP 200 → **计费**。包含「查无结果」（`data` 为 null，如 ID 不存在或筛选无命中）——
  请求已送达蒲公英，同样扣费，不要因为拿不到数据就重试
- HTTP 400 → 不计费（参数格式非法，或上游资源不足/异常）

# [English]
### Purpose:
- Fans growth curve over time ("Fans Analysis → Fans Trend")
### Request Body Parameters:
- user_id: **required**, blogger user ID
- increase_type: 1=**cumulative total** (default), 2=**daily increment**
- date_type: 1=last 30 days (default), 2=last 60 days
### Return:
- list[]: daily data points
- fansNumInc: net growth over the period
- fansNumIncRate: growth rate over the period
### Tip:
- Defaults match the PGY web page (cumulative total + last 30 days)
- Pass increase_type=2 for the daily-increment curve

### 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]
```json
// ① 累计粉丝数曲线（默认，近 30 日）
{"user_id": "5c668b3e0000000012021605"}

// ② 每日新增曲线，近 60 日
{"user_id": "5c668b3e0000000012021605", "increase_type": 2, "date_type": 2}

// ③ 累计曲线拉到近 60 日
{"user_id": "5c668b3e0000000012021605", "date_type": 2}
```

`increase_type=2` 的曲线出现孤立尖峰，通常意味着买量或蹭到热点，
选号时值得再看一眼那几天的笔记。

Isolated spikes in the daily-increase curve usually mean bought traffic or a viral hit.

## Request body

- FansHistoryReq
  - `user_id` string, required: 博主用户ID/Blogger user ID
  - `increase_type` 1 | 2: 曲线口径 1=粉丝总量(默认，累计) 2=粉丝增量(每日新增)/Curve: 1=total, 2=daily increment
  - `date_type` 1 | 2: 时间范围 1=近30日(默认) 2=近60日/Date range: 1=last 30d, 2=last 60d

## Response `200`

Successful Response

- ResponseModel
  - `code` integer: HTTP status code | HTTP状态码
  - `request_id` string, nullable: Unique request identifier | 唯一请求标识符
  - `message` string: Response message (EN-US) | 响应消息 (English)
  - `message_zh` string: Response message (ZH-CN) | 响应消息 (中文)
  - `support` string: Support message | 支持消息
  - `time` string: The time the response was generated | 生成响应的时间
  - `time_stamp` integer: The timestamp the response was generated | 生成响应的时间戳
  - `time_zone` string: The timezone of the response time | 响应时间的时区
  - `docs` string, nullable: Link to the API Swagger documentation for this endpoint | 此端点的 API Swagger 文档链接
  - `cache_message` string, nullable: Cache message (EN-US) | 缓存消息 (English)
  - `cache_message_zh` string, nullable: Cache message (ZH-CN) | 缓存消息 (中文)
  - `cache_url` string, nullable: The URL to access the cached result | 访问缓存结果的 URL
  - `router` string: The endpoint that generated this response | 生成此响应的端点
  - `params` unknown
  - `data` unknown

## Other responses

- `422`: Validation Error

## Changes

- **2026-10-08** `96a122a5f220`: 2 info
  - added the optional property `detail/items/ctx` to the response with the `422` status
  - added the optional property `detail/items/input` to the response with the `422` status
- **2026-09-01** `50f9ec6e1cd3`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi/changes/api/v1/xiaohongshu/pgy/get_blogger_fans_history/post.md)

---

[API](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi.md) - [All operations](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi/llms.txt) - [OpenAPI document](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi/revisions/86a3483c705a?raw)