What the Xiaohongshu All API does and who it is for
Xiaohongshu (RedNote / 小红书) has no official public API, so third-party proxies like this one fill the gap for teams that need structured access to its data. The Xiaohongshu All API surfaces four functional areas — notes, comments, users, and search — which together cover the most common data retrieval patterns: pulling content details, reading engagement signals through comments, profiling creators, and running keyword or user searches.
The primary audience is builders working on influencer marketing platforms, social listening tools, e-commerce competitive intelligence dashboards, and content aggregators that include Chinese social media alongside Douyin or Weibo. The provider also lists Taobao, Tmall, JD, Pinduoduo, Douyin, Kuaishou, Shopee, Lazada, and SHEIN in its broader keyword set, suggesting the same vendor supplies APIs for those platforms too — useful context if you plan to pull data from multiple Chinese commerce or social platforms under one account.
Endpoint walkthrough
The API exposes 13 GET endpoints grouped into four categories. All endpoints follow the pattern /api/xiaohongshu/{resource}/{version}.
Note endpoints
The note group contains five endpoints, all variants of get-note-detail (v1, v2, v4, v5) plus a share-url-transfer/v1. The multiple versions of note detail are not quality tiers — the provider explicitly states that different versions represent different underlying data sources or response formats, often provided as redundancy when platform restrictions affect one source. If one version returns empty or errored data, you can fall back to another. The share URL transfer endpoint resolves the short-link format that Xiaohongshu generates when users share posts externally (the xhslink.com style URLs), converting them into resolvable note identifiers your downstream calls can use.
Comment endpoints
Three endpoints cover comment retrieval: get-note-comment (v2 and v4) fetches top-level comments on a note, while get-note-sub-comment/v2 retrieves threaded replies under a specific parent comment. This two-level structure mirrors how Xiaohongshu displays comment threads natively and gives you the data needed to reconstruct full conversation context, which matters for sentiment analysis and community research.
User endpoints
Two endpoints cover creator profiles: get-user/v3 returns profile-level data for a Xiaohongshu user, and get-user-note-list/v4 retrieves the paginated list of notes published by that user. Together these form the backbone of any creator research or KOL profiling workflow — you can identify a creator, fetch their metadata, and then enumerate their published content.
Search endpoints
The search group offers search-note/v2 for keyword-based note discovery, search-user/v2 for finding creator accounts by name or keyword, and search-recommend/v1 for retrieving search recommendations (likely the autocomplete or trending query suggestions surface). The recommend endpoint is particularly handy for trend monitoring because it reflects what the platform itself is surfacing as popular search terms at a given moment.
Performance characteristics
The API reports an average latency of 633 ms and a 98% success rate across the marketplace. The latency reflects the reality of proxying against a live platform rather than a dedicated data warehouse — expect individual calls to vary, and plan accordingly if you are building user-facing features that depend on real-time responses. The 98% success rate is solid for this category of third-party scraping proxy; the 2% failure budget is worth accounting for with retry logic, especially since the provider also recommends switching between versioned endpoints as a fallback strategy.
Pricing
| Plan | Monthly cost | Requests per month | Cost per request |
|---|---|---|---|
| BASIC | $0 | 20 | — |
| PRO | $39.99 | 1,800 | ~$0.022 |
| ULTRA | $399.99 | 19,000 | ~$0.021 |
| MEGA | $799.99 | 40,000 | ~$0.020 |
The BASIC tier's 20 requests per month is enough to verify that the API returns the data shape you need — nothing more. A note-detail call plus a comment call plus a user lookup will eat through a meaningful fraction of that allowance in a single test session. Do not plan any production use case around the free tier.
PRO at $39.99 / 1,800 requests works out to roughly 60 requests per day on average. That is sufficient for a small monitoring tool checking a curated list of creators or topics daily, but insufficient for anything that involves bulk backfilling or high-frequency polling. ULTRA and MEGA reduce the per-request cost only marginally (~$0.001 difference), so the main reason to step up tiers is volume, not economics.
Compared with other Chinese social-platform data APIs on the same marketplace, these price points are on the higher end per request, which reflects the difficulty of maintaining reliable access to a platform that does not offer an official API.
Practical use cases
Creator/KOL research: Combine get-user/v3 and get-user-note-list/v4 to build profiles of potential brand partners — follower counts, note frequency, and content themes — without manual browsing.
Content monitoring: Use search-note/v2 on brand keywords, product names, or competitor terms at regular intervals to track organic mentions and emerging narratives on Xiaohongshu.
Sentiment and community analysis: Chain get-note-comment/v2 and get-note-sub-comment/v2 to pull full comment threads for NLP pipelines; the two-tier structure preserves conversational context.
Trend detection: Poll search-recommend/v1 periodically to capture which topics the platform is promoting in search, giving early signals on trending categories relevant to your market.
Link resolution pipeline: If your data source produces Xiaohongshu share links (from user-generated content, social listening feeds, or manual curation), share-url-transfer/v1 lets you canonicalize them before passing them to detail endpoints.
Limitations and things to check before integrating
Because this is a third-party proxy rather than an official API, a few considerations apply. Platform-side changes to Xiaohongshu's internal structure can break one or more versioned endpoints without notice; the multi-version design partially mitigates this, but you should build error handling that can gracefully degrade or alert you when a version stops returning data. The provider recommends contacting their support team for persistent errors rather than offering a self-serve status page — factor that into your incident response planning.
Request quotas reset monthly, not daily or hourly, so there are no stated rate limits per second or per minute in the available data. Clarify burst behavior with the provider before designing any high-throughput ingestion job that fires many requests in a short window.
Full endpoint documentation, parameter schemas, and response structures live at the provider's external docs site rather than inline on the marketplace listing. Review those docs carefully before committing to a plan, since the exact fields returned by each version are not described in the listing itself.
Getting started
Subscribe to the BASIC plan to obtain API credentials at no cost. Use the share-url-transfer/v1 endpoint as a first test — it takes a share URL as input and returns a resolved identifier, making it easy to confirm authentication is working without consuming a note-detail quota call. Once you have confirmed the response format from the docs matches your data model requirements, the path to PRO is straightforward through the marketplace billing flow. Keep a fallback version in your configuration (for example, defaulting to v2 of note detail and falling back to v4 on non-200 responses) so that routine platform disruptions do not take your integration down entirely.
