Legal
Terms of Use
Last updated: July 15, 2026
These terms apply to use of XHS Data API through RapidAPI. By subscribing to or using the API, you agree to these terms.
1. Service scope
The API provides normalized access to data exposed through public Xiaohongshu/RedNote note and author pages. XHS Data API is an independent service and is not affiliated with, endorsed by, sponsored by, or operated by Xiaohongshu/RedNote.
2. Permitted use
You may use the API for lawful research, analytics, application features, and internal business purposes when you have an appropriate legal basis. You are responsible for your application, end users, notices, consent, data handling, and compliance with applicable laws, third-party rights, and source-platform terms.
3. Prohibited use
You must not use the API to:
- harass, stalk, threaten, discriminate against, or unlawfully surveil any person;
- collect credentials, private data, or data not intentionally exposed by the public source;
- send spam, manipulate engagement, impersonate others, or facilitate fraud;
- bypass access controls, verification, technical restrictions, or source-platform security;
- overload, disrupt, reverse engineer, probe, or attack the API or its upstream services;
- share, transfer, publish, or resell API credentials; or
- conceal prohibited activity or use returned data in violation of law or third-party rights.
4. Public data and retention
Public availability does not remove your legal obligations. Collect and retain only the data needed for your stated purpose. Honor applicable access, correction, deletion, and objection rights. Do not treat the API as permanent storage or as an authoritative identity, eligibility, credit, employment, housing, insurance, or legal-decision source.
5. Availability and data quality
The API is provided on a commercially reasonable, as-available basis. Upstream pages, public-link tokens, schemas, field coverage, and access rules can change. Values may be unavailable and returned as null. Signed or temporary media URLs can expire. No guarantee is made that any upstream resource, field, token, cursor, job result, or media URL will remain available.
6. Rate limits and fair use
RapidAPI plan limits and gateway rules apply. You must respect HTTP status codes, Retry-After, cursor rules, polling intervals, and documented batch limits. Attempts to evade limits or create excessive upstream load are prohibited.
7. Security
Keep RapidAPI credentials confidential and report suspected compromise promptly through the RapidAPI support channel. Do not place credentials in public code, logs, screenshots, client-side applications, or shared documents.
8. Suspension and termination
Access may be limited, suspended, or terminated for abuse, security risk, nonpayment, legal requirements, source-platform risk, or material breach of these terms. Where practical, reasonable notice will be provided unless immediate action is required.
9. Disclaimer and liability
To the maximum extent permitted by applicable law, the service is provided without warranties of uninterrupted availability, merchantability, fitness for a particular purpose, or non-infringement. You are responsible for validating returned data before relying on it. Liability is limited to the amount you paid for the API during the three months preceding the event giving rise to the claim, except where such limitation is prohibited by law.
10. Changes
These terms may be updated to reflect service, legal, security, or upstream changes. The current version will be published with the API listing or documentation. Continued use after an update constitutes acceptance of the revised terms.
11. Support
For support, suspected credential compromise, data-rights requests, or questions about these terms, contact the provider through the RapidAPI support or messaging channel and include the relevant data.request_id when applicable. Never send cookies, storage state, or complete credentials in a support message.