Xiaohongshu Follower list API

POST

API health

Status data for this API is temporarily unavailable, so its recent state is unknown. This does not mean it is down.

List the followers of a Xiaohongshu account by its 24-character user_id or profile link. Each follower has user_id, nickname, avatar, profile link, follower count and note count. A page usually holds 19 to 20 people; page with next_page_token. Many accounts hide their follower list, and then the call fails and is refunded.

Price $5.56 per 1,000 requests ($0.005556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Please help me write a data collection script with the EveryInfra Xiaohongshu Follower list endpoint (xiaohongshu/followers_list).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to xiaohongshu and action to followers_list, and put the parameters inside params.
- Required parameters:
- user_id: Whose followers to list: the 24-character user_id that profile or search_users returns, or a profile link https://www.xiaohongshu.com/user/profile/<ID>. Many accounts hide their follower list.
- Optional parameters:
- page_token: Page token. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received, with the other parameters unchanged. A page usually holds 19 to 20 people and is one call.
- Returns a list of records. Main fields of each record: user_id, nickname (Display name of the account), avatar_url, url (The record's link on Xiaohongshu), follower_count (Follower count), note_count (Number of notes this follower has poste…), of_user (Which account this row is a follower of…), next_page_token (Page token (search, comments, sub_comme…).
- Example request body:
{
"platform": "xiaohongshu",
"action": "followers_list",
"params": {
"user_id": "59dcceac20e88f3035edb060"
}
}
- Price: $5.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`xiaohongshu`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`followers_list`	Capability identifier, fixed value.
`user_id`	body.params	`string`	Yes	-	Whose followers to list: the 24-character user_id that `profile` or `search_users` returns, or a profile link https://www.xiaohongshu.com/user/profile/<ID>. Many accounts hide their follower list; then the call fails and is refunded.
`page_token`	body.params	`string`	No	-	Page token. Leave it out for the first page, then pass back the previous response's `next_page_token` exactly as received, with the other parameters unchanged. A page usually holds 19 to 20 people and is one call; the last page has no `next_page_token`.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "xiaohongshu",
  "action": "followers_list",
  "params": {
    "user_id": "59dcceac20e88f3035edb060"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.

json

{
  "id": "req_…",
  "platform": "xiaohongshu",
  "action": "followers_list",
  "results": [
    {
      "user_id": …,
      "nickname": …,
      "avatar_url": …,
      "url": …,
      "follower_count": …,
      "note_count": …,
      "of_user": …,
      "next_page_token": …,
      "platform": …
    }
  ],
  "next_page_token": …,
  "pagination": { … },
  "count": …,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`user_id`	User's unique ID on the platform.
`nickname`	Display name of the account.
`avatar_url`	Avatar image link. Some platforms return sized CDN links that can expire.
`url`	The record's link on Xiaohongshu. Links from search, note, profile and hashtag usually carry an access token, so they open in a signed-out browser (the token expires; call again for a fresh link). Note links from user_posts carry no token and need one to open in a browser: call note with the note ID to get a link that opens. Profile links from search_users carry no token either; call profile with the user_id for one that opens. Note links from pgy_content_square carry a token, except with `keyword`, where they carry none.
`follower_count`	Follower count. Exact on profile. Approximate on search_users: the list shows a rounded figure (12,000 appears as 1.2 × 10,000), converted to a whole number. null means not public or not recognized, not zero.
`note_count`	Number of notes this follower has posted (followers_list).
`of_user`	Which account this row is a follower of (followers_list): the user_id in the request.
`next_page_token`	Page token (search, comments, sub_comments, user_posts, search_users, hashtag): pass it back unchanged as page_token, with the other parameters the same, to fetch the next page.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

401: Missing or invalid key.
402: Insufficient balance. Top up first.
422: Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429: Per-minute request limit reached. Wait for Retry-After, then try again.
503: Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty: No data. No charge.

Errors