Follower history fields and sources
Follower history fields and sources. Follow concrete contracts, examples and reviewable steps using Xiaohongshu (RedNote).
Copy the agent prompt manually
Object and null semantics
Follower history (follower_history) is referenced by 1 capabilities across 1 platforms. Shared names help organize records; they do not guarantee identical data coverage.
Preserve identifiers as strings. Null, absent, zero and empty arrays mean different things. Fields under ext are platform extensions, not universal guarantees.
Complete field paths
Field facts come from the preserved public contracts. The table merges platform extensions and identifies the platforms whose contracts declare each field.
| Field path | Type | Requirement | Declaring platforms |
|---|---|---|---|
| creator_id | string | null | Optional in contract | Xiaohongshu (RedNote) |
| days | integer | null | Optional in contract | Xiaohongshu (RedNote) |
| gained | integer | null | Optional in contract | Xiaohongshu (RedNote) |
| growth | number | null | Optional in contract | Xiaohongshu (RedNote) |
| points | array | null | Optional in contract | Xiaohongshu (RedNote) |
| points[].date | string | null | Optional in contract | Xiaohongshu (RedNote) |
| points[].followers | integer | null | Optional in contract | Xiaohongshu (RedNote) |
| approximate | array | null | Optional in contract | Xiaohongshu (RedNote) |
| approximate[].field | string | null | Optional in contract | Xiaohongshu (RedNote) |
| approximate[].kind | string | null | Optional in contract | Xiaohongshu (RedNote) |
| ext | object | Optional in contract | Xiaohongshu (RedNote) |
Capabilities returning this object
| Capability | Object | Shape | Pagination |
|---|---|---|---|
| xiaohongshu.pgy.creators.followers.history | Follower history | item | No cursor |
Clear inputs. Inspectable output.
Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.
Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.
Download contract example (no execution) ↗For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗