Xiaohongshu (RED) Account Profile
Give it a Xiaohongshu user ID and get back the account's public profile: display name, RED ID, bio, follower and following counts, likes-and-collects total, note count, verification status and location.
Overview
Need to size up a Xiaohongshu (RED) creator or brand account before you work with it? Give this app the account's user ID and it reads the public profile page for you, returning one tidy record: display name, RED ID, bio, profile and banner images, follower and following counts, the likes-and-collects total, note count, verification status, declared gender, location and the profile tag strip.
Profile figures on Xiaohongshu are the first thing a marketing, PR or business-development team checks, but they live inside an app that is awkward to query at scale. This app turns a profile page into a row of data you can drop into a spreadsheet, a CRM or an influencer database, with the same fields every time, so account vetting, KOL shortlisting and audience tracking stop being screenshot work.
Data notes
Each record is read directly from the account's public profile page at the time the task runs, so every number is a snapshot of that moment, not a daily average or a historical series. The likes-and-collects total is the single combined figure Xiaohongshu shows on the profile; a separate collects figure is only filled when the platform reports it, and is otherwise 0. The note count is the number of notes counted on the profile page, which can differ from the original-content count shown in the profile tags. The location is the region the account chooses to display, written in Chinese as it appears on the page, and may be empty. Only publicly visible profile information is covered: notes, comments, follower lists and anything that requires logging in or following the account are not included. Accounts that have been deleted, banned or made unavailable come back as a record flagged as no data with the other fields empty.
What a result looks like
Each record is one Xiaohongshu account:
| Display name | RED ID | Followers | Likes and collects | Note count | Verified |
|---|---|---|---|---|---|
| 优篮子Ulanzi老板 | Ulanzi2023 | 38050 | 177864 | 1080 | No |
| 闹闹不是泡泡 | 7416608498 | 3426 | 111332 | 421 | No |
Other fields include User ID, Bio, Profile URL, Avatar URL, Banner URL, Following, Collects, Gender code, Location, Profile tags, Collected at and No data.
Use cases
- When shortlisting creators for a campaign, rank candidates by "Followers" and "Likes and collects", then divide the two to get an engagement-per-follower ratio that separates genuinely active audiences from inflated follower counts.
- When vetting a brand or partner account, read "Verified", "Bio", "Location" and "Profile tags" together to confirm the account is the official one, what it says it does and where it operates before you reach out.
- When tracking an account you already work with, run the task on a regular schedule and compare "Followers", "Note count" and "Likes and collects" between runs to see whether posting cadence and audience growth are moving in the right direction.
- When building an influencer database, store "User ID" as the stable key and "RED ID", "Display name" and "Avatar URL" as the human-friendly labels, since handles and nicknames can change while the user ID does not.
Scope & Boundaries
One account per task and at most one record per task; public profile data only, no notes, comments or follower lists.
- Good for
- When you have a Xiaohongshu user ID and need the account's current public profile figures (followers, following, likes and collects, note count) in one record
- When vetting a creator or brand account before a collaboration and you need verification status, bio and location alongside the audience numbers
- When tracking the same account over time by running the task periodically and comparing follower and interaction counts
- Do not use for
- When you need the account's notes, comments or follower lists rather than the profile summary
- When you only have a RED ID (the handle shown on the profile page) or a nickname and not the 24-character user ID from the profile URL
- When you need many accounts at once in a single call; this app handles one account per task, so submit one task per account
Failure Handling
Failure and retry behavior declared by the author. We recommend including it in your system prompt when integrating.
- 1A completed task with an empty result or a record flagged as no data usually means the user ID does not exist, the account is deleted or banned, or the profile is otherwise unavailable; double-check the ID from the profile URL before retrying
- 2A task that ends in failure or expiry can be resubmitted as is; if it fails again, wait a few minutes before the next attempt
- 3Authentication and authorization errors are not retryable; they indicate a credential problem on the publisher side, so contact the publisher instead of retrying
- 4Rate-limit errors are retryable after a short pause; spread out large batches of tasks instead of submitting them all at once
Input
Parameters required to call this app, generated from the input.schema in manifest.json.
| Field | Business name | Type | Required | Default | Enum / Constraints | Example | Description |
|---|---|---|---|---|---|---|---|
| account_id | Xiaohongshu user ID | string | Yes | — | — | 55c8ae2762a60c7e4bb45331 | The 24-character user ID of the Xiaohongshu account, taken from the end of its profile URL https://www.xiaohongshu.com/user/profile/<user ID>. This is not the RED ID shown on the profile page; an ID that does not exist yields an empty result. |
Output
Field structure of a single record, generated from the output.schema in manifest.json.
| Field | Business name | Type | Example | Description |
|---|---|---|---|---|
| account_id | User ID | string | 55c8ae2762a60c7e4bb45331 | The account's 24-character Xiaohongshu user ID, the same value that was submitted. |
| account_name | Display name | string | 优篮子Ulanzi老板 | The nickname the account currently shows on its profile page. |
| screen_name | RED ID | string | Ulanzi2023 | The public handle shown as the RED ID on the profile page; it can be changed by the account owner. |
| account_url | Profile URL | string | https://www.xiaohongshu.com/user/profile/55c8ae2762a60c7e4bb45331?xsec_token=YBq9XViMxpUwYTUk2SHYqkJWilTF4Gaj_2lo2e6ujLst0=&xsec_source=app_share | Link to the account's profile page on Xiaohongshu. |
| avatar_url | Avatar URL | string | https://sns-avatar-qc.xhscdn.com/avatar/1040g2jo30trs1q3l4u004129jvn2ekphu59c720?imageView2/2/w/540/format/webp | Link to the account's current profile picture. |
| banner_image_url | Banner URL | string | https://sns-avatar-qc.xhscdn.com/user_banner/1040g2k031is9321s1e004129jvn2ekphghlha7g?imageView2/2/w/540/format/jpg&ap=28&sc=USR_BG | Link to the background banner image at the top of the profile page. |
| bio | Bio | string | @优篮子Ulanzi 主理人 欢迎大家提建议 投资 纳贤 听劝 创业孵化 都可以✉️我 | The self-introduction text on the profile page, with original line breaks preserved. |
| is_verified | Verified | boolean | false | Whether the account carries a Xiaohongshu verification badge. |
| follower_count | Followers | integer | 38050 | Number of followers shown on the profile page at collection time. |
| following_count | Following | integer | 2684 | Number of accounts this account follows, as shown on the profile page at collection time. |
| interaction_count | Likes and collects | integer | 177864 | Combined total of likes and collects the account's notes have received, as shown on the profile page. |
| note_count | Note count | integer | 1080 | Number of notes counted on the account's profile page at collection time. |
| collected_count | Collects | integer | 0 | Number of collects reported separately for the account; 0 when Xiaohongshu only reports the combined likes-and-collects total. |
| gender_code | Gender code | integer | 0 | Gender declared on the profile: 0 = male, 1 = female, 2 = not specified. |
| location | Location | string | 广东 | The region shown on the profile page, usually a province or city name in Chinese; empty when the account does not display one. |
| profile_tags | Profile tags | string | [{"icon": "http://ci.xiaohongshu.com/icons/user/gender-male-v1.png", "iconSize": null, "link": null, "name": null, "tagType": "info"}, {"icon": null, "iconSize": null, "link": null, "name": "广东", "tagType": "location"}, {"icon": null, "iconSize": null, "link": null, "name": "摄影博主", "tagType": "profession"}, {"icon": "https://sns-avatar-qc.xhscdn.com/avatar/1040g2jo31793qa0d3u5g5nqphi3g97c59l4tvvg?imageView2/2/w/80/format/jpg", "iconSize": 12, "link": "xhsdiscover://user/5f598c870000000001009d85?tab=goods", "name": "优篮子Ulanzi•品牌创始人", "tagType": "brandManager"}, {"icon": null, "iconSize": null, "link": null, "name": "290条原创内容", "tagType": "original"}] | The tag strip under the bio (profession, location, brand role, original-content count and similar) as one JSON-encoded text; parse it if you need individual tags. |
| crawl_time | Collected at | string | 2026-08-27T14:15:48 | Date and time the profile was read, in the form 2026-08-27T14:15:48. |
| no_data | No data | boolean | false | True when the profile could not be read for the submitted ID; the other fields are then empty. |
Record Schema
Output is returned record by record. detail.output.idFieldHint
{
"type": "object",
"properties": {
"account_id": {
"type": "string",
"title": "User ID",
"description": "The account's 24-character Xiaohongshu user ID, the same value that was submitted.",
"prefill": "55c8ae2762a60c7e4bb45331"
},
"account_name": {
"type": "string",
"title": "Display name",
"description": "The nickname the account currently shows on its profile page.",
"prefill": "优篮子Ulanzi老板"
},
"screen_name": {
"type": "string",
"title": "RED ID",
"description": "The public handle shown as the RED ID on the profile page; it can be changed by the account owner.",
"prefill": "Ulanzi2023"
},
"account_url": {
"type": "string",
"title": "Profile URL",
"description": "Link to the account's profile page on Xiaohongshu.",
"prefill": "https://www.xiaohongshu.com/user/profile/55c8ae2762a60c7e4bb45331?xsec_token=YBq9XViMxpUwYTUk2SHYqkJWilTF4Gaj_2lo2e6ujLst0=&xsec_source=app_share"
},
"avatar_url": {
"type": "string",
"title": "Avatar URL",
"description": "Link to the account's current profile picture.",
"prefill": "https://sns-avatar-qc.xhscdn.com/avatar/1040g2jo30trs1q3l4u004129jvn2ekphu59c720?imageView2/2/w/540/format/webp"
},
"banner_image_url": {
"type": "string",
"title": "Banner URL",
"description": "Link to the background banner image at the top of the profile page.",
"prefill": "https://sns-avatar-qc.xhscdn.com/user_banner/1040g2k031is9321s1e004129jvn2ekphghlha7g?imageView2/2/w/540/format/jpg&ap=28&sc=USR_BG"
},
"bio": {
"type": "string",
"title": "Bio",
"description": "The self-introduction text on the profile page, with original line breaks preserved.",
"prefill": "@优篮子Ulanzi 主理人 欢迎大家提建议\n投资 纳贤 听劝 创业孵化 都可以✉️我"
},
"is_verified": {
"type": "boolean",
"title": "Verified",
"description": "Whether the account carries a Xiaohongshu verification badge.",
"prefill": false
},
"follower_count": {
"type": "integer",
"title": "Followers",
"description": "Number of followers shown on the profile page at collection time.",
"prefill": 38050
},
"following_count": {
"type": "integer",
"title": "Following",
"description": "Number of accounts this account follows, as shown on the profile page at collection time.",
"prefill": 2684
},
"interaction_count": {
"type": "integer",
"title": "Likes and collects",
"description": "Combined total of likes and collects the account's notes have received, as shown on the profile page.",
"prefill": 177864
},
"note_count": {
"type": "integer",
"title": "Note count",
"description": "Number of notes counted on the account's profile page at collection time.",
"prefill": 1080
},
"collected_count": {
"type": "integer",
"title": "Collects",
"description": "Number of collects reported separately for the account; 0 when Xiaohongshu only reports the combined likes-and-collects total.",
"prefill": 0
},
"gender_code": {
"type": "integer",
"title": "Gender code",
"description": "Gender declared on the profile: 0 = male, 1 = female, 2 = not specified.",
"prefill": 0
},
"location": {
"type": "string",
"title": "Location",
"description": "The region shown on the profile page, usually a province or city name in Chinese; empty when the account does not display one.",
"prefill": "广东"
},
"profile_tags": {
"type": "string",
"title": "Profile tags",
"description": "The tag strip under the bio (profession, location, brand role, original-content count and similar) as one JSON-encoded text; parse it if you need individual tags.",
"prefill": "[{\"icon\": \"http://ci.xiaohongshu.com/icons/user/gender-male-v1.png\", \"iconSize\": null, \"link\": null, \"name\": null, \"tagType\": \"info\"}, {\"icon\": null, \"iconSize\": null, \"link\": null, \"name\": \"广东\", \"tagType\": \"location\"}, {\"icon\": null, \"iconSize\": null, \"link\": null, \"name\": \"摄影博主\", \"tagType\": \"profession\"}, {\"icon\": \"https://sns-avatar-qc.xhscdn.com/avatar/1040g2jo31793qa0d3u5g5nqphi3g97c59l4tvvg?imageView2/2/w/80/format/jpg\", \"iconSize\": 12, \"link\": \"xhsdiscover://user/5f598c870000000001009d85?tab=goods\", \"name\": \"优篮子Ulanzi•品牌创始人\", \"tagType\": \"brandManager\"}, {\"icon\": null, \"iconSize\": null, \"link\": null, \"name\": \"290条原创内容\", \"tagType\": \"original\"}]"
},
"crawl_time": {
"type": "string",
"title": "Collected at",
"description": "Date and time the profile was read, in the form 2026-08-27T14:15:48.",
"prefill": "2026-08-27T14:15:48"
},
"no_data": {
"type": "boolean",
"title": "No data",
"description": "True when the profile could not be read for the submitted ID; the other fields are then empty.",
"prefill": false
}
},
"required": [],
"additionalProperties": false
}Integration
This app can be integrated via MCP, API, SDK, or file export — all channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API Key (long-lived, created in the Open Platform console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way.
With the MCP (Model Context Protocol), you can call this app directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.
Client config
Replace the value after Bearer with your long-lived API Key. Works in any client, CI, or headless environment.
{
"mcpServers": {
"5vvv22tx__xiaohongshu-account-info": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=5vvv22tx/xiaohongshu-account-info",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Let AI set it up for you
Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client — it will complete the setup its own way. (The prompt asks the AI to request your API Key from you, so credentials never end up in chat history or shared configs.)
detail.access.mcp.composeHint
Pricing
Charged once per submitted task, regardless of how many records are returned.
Multiple billing events accumulate independently — see each item for details. Failed tasks are not charged.
Try It Now
Fill in the parameters and run — results come from a real call.