Xiaohongshu APIxiaohongshu.com ↗
Access Xiaohongshu note content, user profiles, and explore feed data via a clean REST API. Retrieve posts, images, video URLs, tags, and engagement stats.
What is the Xiaohongshu API?
This API exposes 3 endpoints covering Xiaohongshu (Little Red Book) note content and creator profiles. The get_note_detail endpoint returns a full note record — title, description, images, video stream URLs, tags, creation timestamp, and interaction metadata — given a note_id and its paired xsec_token. The get_user_profile endpoint returns public creator data including follower counts, bio, gender, and Red ID, and list_feed supplies a rotating batch of explore-feed note summaries.
curl -X GET 'https://api.parse.bot/scraper/112e2db4-437f-4511-96f5-f0f62d23a010/get_note_detail?note_id=6a3dd2d8000000000f028736&xsec_token=ABRXNwYgMPDY3C0l-X8AdxgESESUuBuTelkvgtZU_65Wc%3D' \ -H 'X-API-Key: $PARSE_API_KEY'
Fetches a single note full content by its ID. Returns title, description, images, video (when present), tags, author info, and interaction stats. Requires both note_id and xsec_token. The token is per-note and cannot be reused across different notes. Video notes include stream URL, duration, and resolution; image notes include an ordered image list with dimensions.
| Param | Type | Description |
|---|---|---|
| note_idrequired | string | The note/post ID, a 24-character hex string. |
| xsec_tokenrequired | string | Per-note security token unique to each note. Cannot be reused across different notes. Obtained from feed data or share links for the specific note. |
{
"type": "object",
"fields": {
"tags": "array of objects with id, name, type",
"time": "integer (creation timestamp in milliseconds)",
"type": "string (normal or video)",
"user": "object with user_id, nickname, avatar",
"title": "string",
"video": "object with duration, url, format, width, height (present only for video notes)",
"images": "array of objects with url, width, height, file_id",
"note_id": "string",
"description": "string (post body text)",
"ip_location": "string (author location at time of posting)",
"interact_info": "object with liked_count, collected_count, comment_count, share_count (all strings, may use Chinese units)",
"last_update_time": "integer (last update timestamp in milliseconds)"
}
}About the Xiaohongshu API
Note Detail and Feed Data
The get_note_detail endpoint accepts two required parameters: a 24-character hex note_id and a xsec_token that is strictly scoped to that note. The response distinguishes between normal (image) and video note types via the type field. Image notes return an images array with url, width, height, and file_id per asset. Video notes additionally return a video object containing url, format, duration, width, and height. Every note includes a user object (author user_id, nickname, avatar), an array of tags with id, name, and type, a millisecond-precision time timestamp, and an ip_location string reflecting the author's posted location.
User Profiles
The get_user_profile endpoint takes a 24-character hex user_id and returns the public creator record: nickname, description (bio), avatar, red_id, gender (0 = male, 1 = female), ip_location, follows (following count), and fans (follower count). Counts may be returned in Chinese shorthand notation — for example 1万+ to represent values above 10,000 — so consumers should handle string parsing rather than expecting raw integers for these fields. A tags array provides profile classification objects with type, optional name, and optional icon fields.
Explore Feed
The list_feed endpoint takes no input parameters and returns a notes array of feed summaries. Each summary includes a note_id, its paired xsec_token, title, type, and a brief user object (user_id, nickname). Because the feed is personalized and partially randomized, results are not stable across successive calls. This endpoint is the natural source for discovering note_id/xsec_token pairs to pass into get_note_detail.
The Xiaohongshu API is a managed, monitored endpoint for xiaohongshu.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when xiaohongshu.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official xiaohongshu.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Collecting Xiaohongshu note content including images and video URLs for content archival or analysis
- Monitoring creator profile stats — follower counts, bio, and Red ID — over time for influencer research
- Sampling the explore feed to identify trending note types and topics by inspecting returned
tags - Pairing
list_feedwithget_note_detailto build a pipeline that enriches feed summaries with full post content - Extracting
ip_locationandtimefields from notes for geographic or temporal content distribution studies - Aggregating tag data from multiple notes to map topic clusters active on the platform
- Pulling author metadata from note responses to link post content to creator profiles without a separate lookup
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Xiaohongshu have an official developer API?+
What is the xsec_token and where do I get it?+
xsec_token is a per-note security token required by get_note_detail. It is scoped to one specific note and cannot be reused across different notes. The list_feed endpoint returns valid note_id/xsec_token pairs together in its response, making it the intended source for these tokens.Does the API return engagement metrics like likes, comments, or saves for a note?+
get_note_detail response includes interaction stats, but the endpoint description does not expose individual like, comment, or save counts as discrete labeled fields in the current schema. The API covers title, description, images, video, tags, author info, timestamp, and ip_location. You can fork this API on Parse and revise it to surface specific engagement count fields if they appear in the source data.Can I search for notes by keyword or hashtag?+
Does the feed endpoint support pagination or filtering by topic?+
list_feed endpoint takes no input parameters and returns a single randomized batch of feed summaries with no pagination or topic-filter controls. The result set varies per call. You can fork this API on Parse and revise it to add cursor-based pagination or category filtering if the underlying feed supports those parameters.