Xiaohongshu Profile Scraper: RedNote Creator Data

Extract public Xiaohongshu (RedNote / XHS / 小红书) profile data from profile URLs, share links, copied share text, or user IDs. This Actor returns creator bios, avatars, public location labels, tags, and follower/following/likes-plus-collections counters when exposed by the page.

It reads desktop and mobile server-rendered pages over HTTP. You do not supply a Xiaohongshu login or login cookies. That does not grant access to private, deleted, restricted, or login-only profiles, and it does not remove Apify account/API authentication requirements.

Supported scope

There is one profile-extraction mode, not keyword search or creator-post pagination. Use it to enrich known creator lists or compare public profile snapshots over time. Fields depend on the source page; a separate verification-status field is not emitted.

The default connection is DIRECT. APIFY_DATACENTER optionally uses Apify's automatic proxy pool. The input does not offer residential proxy groups or arbitrary custom proxy URLs. No downstream Actor is called.

Quick start

In the Actor's Input tab, enter references to profiles you are permitted to collect, then start a run. This illustrative input uses the schema's example profile; it is not a claim that the profile is currently accessible.

{
  "profileUrls": [
    "https://www.xiaohongshu.com/user/profile/65c381340000000011014d37"
  ],
  "connectionMode": "DIRECT",
  "maxConcurrency": 8,
  "maxRequestsPerMinute": 240,
  "maxRequestRetries": 2
}

Accepted references are full /user/profile/<id> URLs, xhslink.com profile share links, copied share text containing a URL, or bare 24-character hexadecimal user IDs. A note share link is not a substitute for a creator profile.

Input fields

Field	Default	Limits and behavior
profileUrls	Schema example profile	Required string array, 1–10,000 entries. Known user IDs and identical normalized URLs are deduplicated before requests.
connectionMode	DIRECT	DIRECT or APIFY_DATACENTER only.
maxConcurrency	8	Integer, 1–30 concurrent crawler requests.
maxRequestsPerMinute	240	Integer, 10–1,200; crawler request-rate setting, not a promised profile throughput.
maxRequestRetries	2	Integer, 0–5 retries per crawler request.

The runtime also recognizes a legacy userIds array when profileUrls is absent; use the documented profileUrls field for new integrations. One profile may require desktop extraction, a mobile follow-up, redirects, or retries.

Output and count semantics

The default dataset contains successful profile records. Apify dataset exports support JSON, CSV, and other formats. Typical fields include:

• success, input, requestedUrl, profileUrl, and userId.
• nickname, redId, bio, avatarUrl, optional avatarLargeUrl, tags, and source-exposed gender/ipLocation labels.
• following, followers, and likesAndCollects, together with the corresponding ...Text, ...LowerBound, and ...IsExact fields.
• countsSource, optional countsNote, and scrapedAt (UTC ISO extraction time, not account creation time).

Exact numeric count fields are only emitted when the parser regards a source value as exact. For abbreviated or + display values, use ...LowerBound and ...Text; the exact numeric field can be absent and ...IsExact is false. These flags describe the parsed source representation, not independently audited live totals. likesAndCollects is the platform's combined “获赞与收藏” total, not likes alone.

The Actor prefers mobile counters when reachable, but can save desktop lower bounds if the mobile follow-up fails. Mobile-only output can omit desktop-only fields. Missing fields are not inferred demographics, verified identity, or contact information.

Limits and failure handling

• Apify Free plan: the developer caps the run at 50 dataset rows and also selects only the first 50 normalized valid profile references. Failed selected inputs can therefore leave fewer than 50 results; later references are not used to fill the gap.
• Paid Apify plans: no developer-set 50-row cap; input limits, charge budgets, runtime limits, and source availability still apply.
• Alias share links that cannot be resolved to an ID before crawling may not deduplicate against another reference to the same profile.
• Invalid or failed input diagnostics are stored in the ERRORS key-value-store record, not as billable dataset rows. Partial runs can succeed with some failed inputs. A run with zero successful profiles is treated as FAILED.
• Blocking, CAPTCHA/login redirects, rate limits, deleted profiles, and page-format changes can prevent collection. Increasing concurrency is not a guarantee of better throughput.

Current pricing

This is pay-per-event pricing. The Free plan is not a zero-priced result tier.

Event	FREE	BRONZE / SILVER / GOLD / PLATINUM / DIAMOND
apify-default-dataset-item — saved profile row	$0.015	$0.003
apify-actor-start — startup event	$0.005	$0.005

The startup event is charged per GB of allocated memory, with a minimum of one event; it is not universally a fixed fee. At the default 256 MB allocation, one minimum startup event applies. A start fee can apply even with no profile results.

Profile rows are saved using Actor.pushData; there is no additional custom per-profile charge in the reviewed runtime. Error records in ERRORS do not create result events. Apify platform usage is paid separately by the running user, including applicable compute, transfer, storage, and proxy usage, even on empty or failed runs. Event fees are not all-inclusive totals.

Confirm the effective plan-specific prices on the Pricing tab. A maximum event-charge budget can truncate an export.

FAQs

Does “no login supplied” mean all profiles are accessible? No. Only data reachable through the public page responses is parsed. The Actor does not provide private-account access or bypass access controls.

Are follower counts always exact? No. Inspect the count exactness flags, original text, and lower-bound fields. Public source counters can also change after extraction.

Can it export creator posts or search by keyword? No. This Actor extracts known creator profiles. Choose a complementary Actor for recent notes or category-based discovery.

Use collected personal data responsibly, comply with applicable laws and platform terms, and minimize retention and redistribution.

Complementary Actors

• Xiaohongshu Creator Notes Scraper — recent notes exposed on known creator pages.
• Xiaohongshu Influencer Finder — category-based creator discovery through public note cards.