Xiaohongshu User Profile Scraper

Turn a public Xiaohongshu (RedNote / 小红书) profile URL, user ID, share link, or Red ID into one structured profile row. You get nickname, Red ID, bio, follower and following counts, likes, IP location, verification, and optional first-page note previews. No Xiaohongshu login or cookies.

This Actor is built for influencer researchers, brand analysts, and agents that already have a creator link and need a cheap, predictable profile lookup before they scrape notes or comments.

Best fit for this Actor

• Enrich a known list of Xiaohongshu creator URLs with follower counts and bios.
• Qualify a RedNote influencer before pulling notes or comment threads.
• Feed MCP or CRM workflows with one row per public profile.

Practical scenario

An influencer-ops analyst pastes https://www.xiaohongshu.com/user/profile/65c381340000000011014d37, leaves includeRecentNotes off, and sets maxProfiles to 1. The run returns one public profile row: nickname, Red ID, bio, followers, likes, and IP location. A deleted or unknown handle finishes SUCCEEDED with VALID_EMPTY and no profile-scraped charge. Creators that clear the size bar can then be sent to the comments or note-detail siblings.

Quick start input

{
  "profileUrls": ["https://www.xiaohongshu.com/user/profile/65c381340000000011014d37"],
  "includeRecentNotes": false,
  "maxProfiles": 1
}

profileUrls accepts /user/profile/{userId} links, xhslink.com share links, bare 24-character user IDs, and Red IDs. Duplicate values are collapsed before any fetch.

Input reference

Field	Type	What it controls
profileUrls	array (required)	Public profile URLs, user IDs, share links, or Red IDs. Example: 65c381340000000011014d37. Max 20 unique values.
includeRecentNotes	boolean	Attach a first-page public notes preview. Default false. This is a grid preview rather than a full posting archive.
maxRecentNotes	integer	Grid notes kept per profile when the preview is on. Default 6, max 12.
maxProfiles	integer	Hard cap after dedupe. Default 20. Prefill 1 keeps quality tests fast.

What data you receive

One dataset item is one public profile.

{
  "inputProfile": "https://www.xiaohongshu.com/user/profile/65c381340000000011014d37",
  "userId": "65c381340000000011014d37",
  "redId": "Patellana",
  "profileUrl": "https://www.xiaohongshu.com/user/profile/65c381340000000011014d37",
  "nickname": "Patella",
  "bio": "Fashion notes",
  "gender": "female",
  "ipLocation": "Shanghai",
  "followerCount": 12000,
  "followingCount": 128,
  "likeCount": 100000,
  "isVerified": false,
  "provider": "scrapfly",
  "scrapedAt": "2026-09-10T12:00:00.000Z"
}

Field	Meaning
nickname + redId	Public display name and Xiaohongshu Red ID
followerCount / followingCount / likeCount	Public counters when Xiaohongshu exposes them
ipLocation	Public IP location label
recentNotes	Optional first-page note preview
sourceUrl / provider	Page and fetch route used for the row

OUTPUT and RUN_SUMMARY in the default key-value store hold outcome, itemsPushed, and chargedEventCounts.

Use through the API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~xiaohongshu-user-profile-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"profileUrls":["https://www.xiaohongshu.com/user/profile/65c381340000000011014d37"],"maxProfiles":1}'

Download rows as JSON, CSV, Excel, or HTML from the Dataset tab.

Use with AI agents through Apify MCP

Look up the public Xiaohongshu profile at https://www.xiaohongshu.com/user/profile/65c381340000000011014d37. Return nickname, redId, followerCount, likeCount, ipLocation, and isVerified. Keep the scope to public profile metadata; route comment threads and note archives to the sibling Actors.

Connect via https://mcp.apify.com. Read OUTPUT.outcome and itemsPushed to interpret empty datasets. Cost signal: about $0.01 per found profile plus platform usage. Missing or deleted handles surface as VALID_EMPTY without a profile-scraped charge.

Connect the workflow

• After you confirm the creator, scrape comment threads with Xiaohongshu Comments Scraper.
• For a specific note URL, use Xiaohongshu Note Detail Scraper.
• When you still need handles, discover notes with Xiaohongshu Search Scraper and then return here for profile enrichment.

Pricing

This Actor uses Pay per event plus Apify platform usage. The live Pricing tab is the current source of truth for billing details.

• apify-actor-start: $0.00005 per run
• profile-scraped: $0.01 per found public profile row

A one-profile prefill is about $0.01 in result events plus compute/proxy usage. Missing or deleted handles have no profile-scraped charge.

How it works

1. Normalize and deduplicate profile URLs, user IDs, share links, and Red IDs.
2. Fetch the public profile page through an anti-bot render path, then a nested public-profile provider, then residential Firefox if needed.
3. Parse nickname, Red ID, counters, IP location, verification, and optional grid notes.
4. Charge profile-scraped for found rows, then write the dataset item.

Best results

• Prefer /user/profile/{userId} URLs that include xsec_token, or xhslink.com share links.
• Keep includeRecentNotes off when you only need identity and audience size.
• A typo or deleted handle finishes SUCCEEDED with VALID_EMPTY and no profile charge.
• Explore/note URLs without a user ID belong on the note-detail or comments Actors.

Builder's note

I found that Xiaohongshu's public web profile still ships __INITIAL_STATE__ with nickname, Red ID, and interaction counters when the anti-bot render path succeeds. Direct datacenter HTTP usually surfaces Xiaohongshu code 300031, so this Actor keeps the owned parser and uses a render provider first, then a nested public-profile Actor, then residential Firefox. That split keeps the product a lean one-row profile SKU rather than a notes archive.

Legal and responsible use

Use this Actor on public Xiaohongshu profile pages you are authorized to process, follow applicable law and Xiaohongshu's terms, and keep the output in your own compliance workflow. This Actor is independent of Xiaohongshu / RedNote. It does not collect DMs, follower rosters, or login-walled data.

Issues and feature requests: use the Actor Issues tab on Apify.