# Xiaohongshu User search API (xiaohongshu.search_users)

- Canonical page: https://everyinfra.com/en/xiaohongshu-api/search_users
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "xiaohongshu", "action": "search_users", "params": {...}}
- Price: $0.005556 per call ($5.56 per 1,000 requests); failed calls and empty results are not charged
- Returns: list, one page of 20 per call (limit is ignored; pass the top-level next_page_token from the response as page_token for the next page)
- Pagination: pass next_page_token back as page_token for the next page, other params unchanged; one call per page, tokens last 24 hours
- Mode: sync; add "mode": "async" for slow tasks

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.

## Health

- Live health (24h percent, hourly and daily trends): https://api.everyinfra.com/api/v1/social/availability?platform=xiaohongshu&action=search_users

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| keyword | not declared | yes | not declared | 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 | enum: 100_to_1k / 10k_to_100k / 1k_to_10k / over_100k / under_100 | no | not declared | 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. |
| page_token | not declared | no | not declared | 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 | enum: business / general / verified_individual | no | not declared | Filters accounts in search_users by type: general (regular user), verified_individual (verified person) or business (verified business). Omit it for no limit. |

## Response fields (items in `results`)

| 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. 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. |
| 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). |

## Example

```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": "咖啡"
  }
}'
```

```python
import os
import requests

response = requests.post(
    "https://api.everyinfra.com/api/v1/social",
    headers={"Authorization": f"Bearer {os.environ['EVERYINFRA_API_KEY']}"},
    json={
        "platform": "xiaohongshu",
        "action": "search_users",
        "params": {
            "keyword": "咖啡",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

Real response to the example request above, captured 2026-10-24T18:28:34Z. `results` and `count` are real with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2 of 20. `id`, `billing` and `quota` differ on every call, so only their shape is shown.

```text
{
  "id": "req_…",
  "platform": "xiaohongshu",
  "action": "search_users",
  "results": [
    {
      "user_id": "•••",
      "nickname": "•••",
      "red_id": "•••",
      "avatar_url": "https://sns-avatar-qc.xhscdn.com/•••",
      "url": "https://www.xiaohongshu.com/•••",
      "follower_count": 456000,
      "is_verified": false,
      "next_page_token": "n1.p2",
      "platform": "xiaohongshu"
    },
    {
      "user_id": "•••",
      "nickname": "•••",
      "red_id": "•••",
      "avatar_url": "https://sns-avatar-qc.xhscdn.com/•••",
      "url": "https://www.xiaohongshu.com/•••",
      "follower_count": 148000,
      "is_verified": true,
      "verification_type": "business",
      "next_page_token": "n1.p2",
      "platform": "xiaohongshu"
    }
  ],
  "next_page_token": …,
  "pagination": { … },
  "count": 20,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}
```

## 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.

## Also

- Capability catalog (no key): https://api.everyinfra.com/api/v1/social/catalog?platform=xiaohongshu
- OpenAPI: https://everyinfra.com/openapi.json · Agents guide: https://everyinfra.com/agents.md