Xiaohongshu Image Note Detail Scraper

Fetch the full detail of a Xiaohongshu image post (note) by note_id or share_text. Returns the normalized title, description, image list, author, and engagement metrics for a single note. One upstream request per run; no pagination needed.

When both note_id and share_text are provided, note_id wins.

Use it together with the other Xiaohongshu Actors

This Actor is one piece of a 4-piece Xiaohongshu toolkit. Run them in sequence to go from a topic, to a single note detail, to its comment thread.

Where in the pipeline	Actor	Console	Use it to
before / step ①	Xiaohongshu Keyword Search Scraper	JECW4SdwsOOgtuobc	step ① — start here to discover noteIds by keyword, then feed one to this Actor
sister Actor / step ②	Xiaohongshu Video Note Detail Scraper	nIGSWsYF5htLotphk	sister Actor — same shape, but for video notes (returns playback URLs)
after / step ③	Xiaohongshu Note Comments Scraper	LNXEA0uuHX70vchNW	step ③ — pull the comment thread for the same noteId

You are here: Xiaohongshu Image Note Detail Scraper (step ②) — run this on its own for pull the full payload for one image note. The other 3 Actors live in their own Apify listings — click their Console links to open them in a new tab.

No Setup Required

No setup required. The upstream API key and base URL are preconfigured in this Actor — no Environment variables to add, no Console setup steps to follow. Just click Start and fill in the input form.

Schema changed? Apify Console caches the input form. Click Reload editor (or hard-refresh) to pick up new fields after a schema bump.

Why Use This Actor

Problem	How This Actor Solves It
You have a Xiaohongshu note URL but no easy way to extract title, images, and engagement stats.	Pass the URL as share_text; get a normalized JSON record back.
You want to enrich your CRM or BI dataset with Xiaohongshu post performance.	One normalized row per run with structured fields and the original payload in rawData.
You need a fast, deterministic way to grab a single note detail without scraping.	One upstream request per run — cheap, predictable, no pagination.

What You Get

A single normalized dataset row with:

• Identifiers — noteId, xsecToken, noteUrl
• Content — title, description, noteType, tags, ipLocation, publishTime
• Media — images[] (each with url, urlDefault, urlPre, width, height, format, livePhoto), coverUrl
• Author — userId, nickname, avatar
• Engagement — likedCount, collectedCount, commentCount, sharedCount
• Provenance — source (note_id or share_text), collectedAt, rawData (full upstream payload)

Plus a SUMMARY record with the note ID, source kind, and request count.

Quick Start

1. Run with Example Input

{
  "note_id": "697c0eee000000000a03c308"
}

Or paste a Xiaohongshu share link or the full app share text (the Actor extracts the URL automatically):

{
  "share_text": "美食推荐 https://www.xiaohongshu.com/explore/64abcdef0000000000ffffff?xsec_token=abc&xsec_source=pc_copy_link 复制打开"
}

2. Export Your Results

The dataset is available as a JSON array; the SUMMARY record is in the default key-value store.

Input Reference

note_id — Note ID

Required	Type	Description
Optional (one of two)	string	Xiaohongshu note ID, up to 64 alphanumeric characters. Wins over share_text when both are provided.

share_text — Share text

Required	Type	Description
Optional (one of two)	string	A Xiaohongshu share link or the full share text from the app. up to 2000 characters; the Actor extracts the first http(s) URL. Use when you don't have the raw note_id.

Output Reference

See "What You Get" above for the full field list. Each row also includes rawData, the unmodified upstream payload, for audit and re-parsing.

Pricing & Limits

• Free tier: 5 runs/day (one detail fetch = one run).
• Paid users: Unlimited runs.
• Hard caps: 1 note per run, 1 upstream request per run. No bulk input — pass a single note at a time.

FAQ

• Can I fetch many notes in one run? No. This Actor is built around one note = one request. Run it multiple times, or use a workflow/scheduler to fan out.
• My share text is missing the URL — what happens? The Actor's extractShareUrl regex needs at least one http(s) link. If you only pasted the title or Chinese characters, it will reject the input.
• I got an empty images array. Some notes are video-only or the author deleted the images. Check noteType and rawData.
• Why is my free run blocked? Free tier is 5 runs/day. Either upgrade your Apify plan, wait until tomorrow, or set APIFY_USER_IS_PAYING=1 (paid tier only).
• Do I need to add an upstream API key? No. This Actor ships with the upstream integration preconfigured — UPSTREAM_API_KEY and UPSTREAM_BASE_URL are baked into the build. No Console setup, no secrets to manage.

Support

Open an issue on the Actor Console page or contact via Discord linked in the upstream SUMMARY.

Actor

• Apify Actor ID: kP7I5XcMAaLxaYj0R
• Console: https://console.apify.com/actors/kP7I5XcMAaLxaYj0R

Changelog

See ./CHANGELOG.md.