> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# How do I review recent follower growth before selecting Xiaohongshu creators?

> Choose totals or daily increments, use consistent 30/60-day windows and preserve returned curves and summaries before investigating content context.

To review a creator's recent follower growth, call `xiaohongshu.pgy.get_blogger_fans_history` with the creator's `user_id`. Set `increase_type` to `1` for the follower-total curve or `2` for daily additions, and set `date_type` to `1` for the last 30 days or `2` for the last 60 days. Compare creators only with the same window and the same curve type.

For example, if one of five coffee creators shows a spike, look up that creator's posts and campaigns around the spike date, then decide whether the spike matters for your collaboration.

## Confirm accounts and use consistent inputs

Reuse the verified `user_id` values from the [candidate workflow](/guides/xiaohongshu-creator-shortlist); do not merge accounts by display name. For each creator, save the request, the collection time and the original response, and use the same parameters for every creator.

Example 60-day daily-increment request for `data:xiaohongshu.pgy.get_blogger_fans_history`:

```bash
curl -sS https://api.beatapi.io/v1/social-data/call \
  -H "Authorization: Bearer $BEATAPI_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"action":"xiaohongshu.pgy.get_blogger_fans_history","params":{"user_id":"<user_id>","date_type":2,"increase_type":2}}' \
  -o creator-follower-increments.json
```

`date_type` and `increase_type` both default to `1`, so a request without them returns the 30-day total curve. `xiaohongshu.pgy.get_blogger_fans_history` takes no arbitrary start or end date, and the 90-day option of another action does not apply here.

## Distinguish totals, daily increments and interval change

| Material                   | Use                                                                   |
| -------------------------- | --------------------------------------------------------------------- |
| Total curve                | Observe account size over the window                                  |
| Daily-increment curve      | Review the platform's daily-increment definition                      |
| `data.data.fansNumInc`     | Retain reported net change for the interval                           |
| `data.data.fansNumIncRate` | Preserve the raw growth-rate representation until its unit is checked |
| `data.data.list`           | Preserve returned point and date evidence                             |

Subtracting adjacent totals gives a locally calculated net change, not the platform's gross gains or losses. When a date is missing, two adjacent records do not represent one day's change.

## Investigate an unusual change

First confirm the date and the curve type, then review the account's posts, campaigns and known data updates around that date. A spike tells you what to investigate; the spike does not tell you the cause.

Compare accounts over the same period. Collaboration fit depends on content, audience and your brief; the follower curve describes only the observed interval.

To hand the task to an assistant with the tools configured, use a prompt such as:

> Save 60-day daily-increment records and interval summaries for these five verified accounts, retaining original values and collection time. Organize changes that can actually be checked and identify dates needing content or campaign context. List unclear periods, units or points separately.

Example: one date is missing between two observations, and the total rose by 200. Report “Up 200 between these two observations” with both dates, and leave the missing day blank. To explain the change, review the posts and known events from that interval.

## Deliver the material

For each account, deliver the parameters, the raw curve, the interval net change, the raw growth-rate value and the dates that need review. Check the internal business status as well as the outer result. Mark an account without a valid response as pending; do not record zero growth.

The date and value keys of each curve point and the scaling of the growth rate are not fixed yet, so this page gives no automatic curve normalization or anomaly labels. Keep and review the actual responses instead of copying a competitor's `points/gained/growth` fields.

Five accounts with one curve each take five queries; the total curve and the daily-increment curve for each account take 10. Estimate the cost with current [pricing](https://beatapi.io/pricing) and reuse saved responses.

[Audience review](/faq/xiaohongshu-audience-quality) · [Creator shortlist](/guides/xiaohongshu-creator-shortlist)