FetchPI
Log in

Guides

Xiaohongshu (RED) API for Developers: Notes, Profiles and Search as JSON

Xiaohongshu data without reverse-engineering the app: profile, notes, comments and search behind one normalized API — the same request model as every FetchPI platform.

Last reviewed

Quickstart

Every request needs one header: Authorization: Bearer $FETCHPI_API_KEY. Create a free key in the console and you can replay every snippet on this page as-is.

curl -s -H "Authorization: Bearer $FETCHPI_API_KEY"   "https://fetchpi.com/v1/xhs/users/{username}?freshness=default"

Why an API for RED at all

Xiaohongshu (小红书 / RED) is where Chinese consumer trends start, but its data surface is an app-private protocol — signature headers, rotating endpoints, layout churn. FetchPI serves the public surfaces as normalized JSON: you call a URL, you get typed records, you never see the app protocol.

The endpoint map

  • GET /v1/xhs/users/{username} — profile.
  • GET /v1/xhs/users/{username}/posts — the notes feed.
  • GET /v1/xhs/posts/{id} — note detail.
  • GET /v1/xhs/posts/{id}/comments — comments.
  • GET /v1/xhs/search/posts — note search.

Working with the records

Notes come back as the same post entity every platform uses — author, text, created_at, metrics, attachments — so a cross-platform trend pipeline treats RED notes like Reddit posts: same fields, same pagination, same freshness parameters. Prices are on the catalog page per capability.