Xiaohongshu User search API

Q: How do I get more than one page of accounts?

Each call returns one page. Take the top-level next_page_token from the response and send it back as page_token, keeping keyword and every filter unchanged; leaving out page_token starts again from the first page. limit is accepted but has no effect here, so paging is how you get more accounts, one call per page.

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Find Xiaohongshu creators and brand accounts by keyword, 20 per page, with nickname, Xiaohongshu ID, follower count and verification type. Filter by follower_range or user_type; follower counts approximate the rounded list figures, so call profile for exact numbers.

Xiaohongshu User search finds accounts by keyword, such as a brand name or a topic word like coffee, and returns creators and brand accounts rather than notes. Each row carries the internal user_id, the nickname, the Xiaohongshu ID in red_id, the avatar, a profile link, the follower count, and whether and how the account is verified. It is the starting point for creator shortlists, competitor mapping and audits of brand accounts on Xiaohongshu.

Narrow results by audience size with follower_range, from under_100 up to over_100k, and keep ordinary users, verified individuals or verified businesses with user_type set to general, verified_individual or business. verification_type is left out for unverified accounts. Profile links from this search carry no access token, so pass the user_id to the Xiaohongshu Details capability for a link a signed-out browser can open, along with exact counts.

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

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Xiaohongshu User search endpoint (xiaohongshu/search_users).

Endpoint contract:
- 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 search_users, and put the parameters inside params.
- Required parameters:
  - keyword: A keyword for finding accounts, such as coffee, a brand name or a topic. It returns users (creators and brand accounts), not notes.
- Optional parameters:
  - follower_range: Filters accounts in search_users by follower count: under_100, 100_to_1k, 1k_to_10k, 10k_to_100k or over_100k. Omit it for no limit. (allowed: 100_to_1k / 10k_to_100k / 1k_to_10k / over_100k / under_100)
  - page_token: Pagination cursor for the comments, sub_comments, search, user_posts, search_users and hashtag actions: pass back the next_page_token value from a row of the previous response to fetch the next page.
  - user_type: Filters accounts in search_users by type: general (regular user), verified_individual (verified person) or business (verified business). Omit it for no limit. (allowed: business / general / verified_individual)
- Returns a list of records. Main fields of each record: user_id, nickname (Display name of the account), red_id (Xiaohongshu ID: the searchable ID the a…), avatar_url, url (The record's link on Xiaohongshu), follower_count (Follower count), is_verified, verification_type (Verification type on search_users and p…), next_page_token (Page token (search, comments, sub_comme…).
- Example request body:
{
  "platform": "xiaohongshu",
  "action": "search_users",
  "params": {
    "keyword": "咖啡"
  }
}
- 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	`search_users`	Capability identifier, fixed value.
`keyword`	body.params	Not declared	Yes	-	A keyword for finding accounts, such as coffee, a brand name or a topic. It returns users (creators and brand accounts), not notes.
`follower_range`	body.params	`enum`	No	-	Filters accounts in search_users by follower count: under_100, 100_to_1k, 1k_to_10k, 10k_to_100k or over_100k. Omit it for no limit.Allowed values`100_to_1k10k_to_100k1k_to_10kover_100kunder_100`
`page_token`	body.params	Not declared	No	-	Pagination cursor for the comments, sub_comments, search, user_posts, search_users and hashtag actions: pass back the next_page_token value from a row of the previous response to fetch the next page; omit it to start from the first page. Each page is one call, billed per request.
`user_type`	body.params	`enum`	No	-	Filters accounts in search_users by type: general (regular user), verified_individual (verified person) or business (verified business). Omit it for no limit.Allowed values`businessgeneralverified_individual`

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": "search_users",
  "params": {
    "keyword": "咖啡"
  }
}'

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

Response example

Field preview

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json

{
  "id": "req_…",
  "platform": "xiaohongshu",
  "action": "search_users",
  "results": [
    {
      "user_id": …,
      "nickname": …,
      "red_id": …,
      "avatar_url": …,
      "url": …,
      "follower_count": …,
      "is_verified": …,
      "verification_type": …,
      "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.
`red_id`	Xiaohongshu ID: the searchable ID the account holder chooses, different from the internal user_id.
`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.
`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.
`is_verified`	Whether the platform verified the account. null means it cannot be determined.
`verification_type`	Verification type on search_users and profile: individual (verified person), business (verified business) or other. Unverified accounts leave this field out.
`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).

FAQ

How do I find a specific Xiaohongshu user?

Search with the account's name or a word closely tied to it, then confirm the match with red_id, the searchable Xiaohongshu ID the account holder chose. Once you have the right row, keep its user_id: the Details and Posts by user capabilities look accounts up by that internal ID rather than by nickname.

Why do follower counts look rounded?

The search list shows follower numbers in rounded form, and follower_count converts that display into a whole number, so a list figure of 1.2 × 10,000 comes back as 12,000. Null means the count was not public or could not be read, not zero. The Xiaohongshu Details capability returns the exact figure.

How do I get more than one page of accounts?

Each call returns one page. Take the top-level next_page_token from the response and send it back as page_token, keeping keyword and every filter unchanged; leaving out page_token starts again from the first page. limit is accepted but has no effect here, so paging is how you get more accounts, one call per page.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).