logo
EN

Xiaohongshu Account Info

Collect profile details, audience metrics, verification, and engagement signals for one Xiaohongshu account

Data collection
Developer
meme_today
Pricing
From $0.003 / record
Last updated
2026-09-16

Overview

A Xiaohongshu account profile brings together identity, audience scale, visible engagement, verification, location, and profile presentation. This Data App turns that profile into one consistent record so teams can compare accounts without manually transcribing names, counts, biographies, images, and verification details.

The result works well as a reusable account snapshot. It keeps the submitted account ID beside the profile returned by the source, making repeated collections easier to join and compare while preserving the source values needed for later analysis.

Data notes

Each result represents the profile collected for the submitted Xiaohongshu account ID. Requested account ID preserves the value used to start the collection, while No data distinguishes an unavailable result from a populated profile. The source can leave individual profile attributes unavailable; those values may be empty even when the rest of the account record is present.

Follower count, Following count, Saved count, Discovery count, Liked count, and Interaction total are snapshots observed at collection time and may change later. Interaction details and Profile tags are retained as source text because they can contain multiple named metrics or tag objects. Collected at, Content last updated, and Source updated at preserve the source timestamps without inferring a timezone.

What the results look like

Each row is one Xiaohongshu account profile snapshot.

Requested account IDAccount nameFollower countInteraction totalVerifiedCollected at
55c8ae2762a60c7e4bb45331优篮子Ulanzi老板38050177864No2026-08-27T14:15:48
643a7d8d000000000d01ab5c闹闹不是泡泡3426111332No2026-08-27T14:31:13

Additional values include Xiaohongshu ID, Profile description, Account URL, avatar and banner links, verification details, Location, account level, and source update times.

Use cases

  • For account benchmarking, compare Follower count, Following count, and Interaction total to understand differences in audience scale and visible engagement.
  • For creator screening, review Account name, Profile description, Verified, Verification details, Location, and Profile tags to organize candidate accounts.
  • For profile monitoring, join repeated snapshots by Requested account ID and compare Follower count, Interaction total, Account name, and Profile description over time.

Scope and boundaries

Each run processes exactly one Xiaohongshu account ID and returns one profile record when data is available.

  • Good for
  • When you need a current profile snapshot for a specific Xiaohongshu account
  • When you need audience size, verification, profile presentation, and visible engagement signals in one record
  • Do not use for
  • When you need a list of posts or comments rather than account-level information
  • When you do not have a Xiaohongshu account ID for the target profile

Failure handling

Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.

  1. 1If no profile data is returned, verify the account ID and confirm that the profile is still available
  2. 2Retry later after rate limiting, temporary service unavailability, or a timeout
  3. 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
  4. 4If authentication fails, verify the API Key configured for the execution environment

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

  • Xiaohongshu account IDaccount_idRequiredstring
    The account ID to collect. Enter one value containing 1 to 512 characters.
    Example55c8ae2762a60c7e4bb45331

Output

Field structure of a single record, generated from the output.schema in manifest.json.

  • Requested account IDsource_account_idstring
    The Xiaohongshu account ID submitted for this collection
    Example55c8ae2762a60c7e4bb45331
  • No datano_databoolean
    Whether the source returned no account profile data for the submitted ID
    Examplefalse
  • Profile descriptionaccount_descriptionstring
    The biography text shown on the Xiaohongshu account profile
    Example@优篮子Ulanzi 主理人 欢迎大家提建议 投资 纳贤 听劝 创业孵化 都可以✉️我
  • Account IDaccount_idstring
    The account identifier returned with the Xiaohongshu profile
    Example55c8ae2762a60c7e4bb45331

Sample data

Generated from output.schema. Fields without a sample value use structural placeholders.

output.example
{
  "source_account_id": "55c8ae2762a60c7e4bb45331",
  "no_data": false,
  "account_description": "@优篮子Ulanzi 主理人 欢迎大家提建议\n投资 纳贤 听劝 创业孵化 都可以✉️我",
  "account_id": "55c8ae2762a60c7e4bb45331",
  "account_name": "优篮子Ulanzi老板",
  "account_screen_name": "Ulanzi2023",
  "account_unique_id": "Ulanzi2023",
  "account_url": "https://www.xiaohongshu.com/user/profile/55c8ae2762a60c7e4bb45331",
  "account_verify_flag": false,
  "account_verify_info": "<account_verify_info>",
  "account_verify_type_code": "0",
  "avatar_url": "https://sns-avatar-qc.xhscdn.com/avatar/1040g2jo30trs1q3l4u004129jvn2ekphu59c720?imageView2/2/w/540/format/webp",
  "banner_image_url": "https://sns-avatar-qc.xhscdn.com/user_banner/1040g2k031is9321s1e004129jvn2ekphghlha7g?imageView2/2/w/540/format/jpg&ap=28&sc=USR_BG",
  "biz_id": "55c8ae2762a60c7e4bb45331",
  "collected_count": 0,
  "content_last_update_time": "<content_last_update_time>",
  "crawl_time": "2026-08-27T14:15:48",
  "discovery_count": 1080,
  "follower_count": 38050,
  "following_count": 2684,
  "gender_code": 0,
  "interaction_count": 177864,
  "interactions": "[{\"count\": \"2684\", \"isPrivate\": false, \"name\": \"关注\", \"toast\": \"\", \"type\": \"follows\"}, {\"count\": \"38050\", \"isPrivate\": false, \"name\": \"粉丝\", \"toast\": \"\", \"type\": \"fans\"}, {\"count\": \"177864\", \"isPrivate\": false, \"name\": \"获赞与收藏\", \"toast\": \"\", \"type\": \"interaction\"}]",
  "level_name": "<level_name>",
  "level_num": 0,
  "liked_count": 0,
  "location_name": "广东",
  "source_update_time": "2026-08-27T14:15:48",
  "tags": "[{\"icon\": null, \"iconSize\": null, \"link\": null, \"name\": \"广东\", \"tagType\": \"location\"}, {\"icon\": null, \"iconSize\": null, \"link\": null, \"name\": \"摄影博主\", \"tagType\": \"profession\"}]",
  "xhs_type": "app"
}

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 Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.

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 config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=meme_today/xiaohongshu-account-info",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}
View my API Keys →

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

Task start

Charged once per submitted run, regardless of how many records are returned.

$0.0001/ run
Returned profile

Charged by the number of records successfully returned. Failed runs are not charged.

$0.003/ record

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
From $0.003 / record