Lifestyle trend snapshots
Use Rednote endpoints to turn lifestyle trend snapshots into repeatable API requests with documented inputs and JSON responses.
Snapshot Rednote's public explore feed with its channel list, keeping every card, like count, and author card dated to the request that returned it.
Explore Rednote's public lifestyle feed: one page of note cards, the dynamic channel list, and public author cards.
Endpoint families
1
Documented params
2
Examples
1
Live catalog snapshot
Active endpoints
1
Methods
GET
Required params
1
Schema refs
1
{
"platform": "Rednote",
"endpoint": "rednote-explore",
"method": "GET",
"path": "/rednote/explore",
"auth": "apiKey"
}Use cases
Explore Rednote's public lifestyle feed: one page of note cards, the dynamic channel list, and public author cards.
Use Rednote endpoints to turn lifestyle trend snapshots into repeatable API requests with documented inputs and JSON responses.
Use Rednote endpoints to turn public note card metadata into repeatable API requests with documented inputs and JSON responses.
Use Rednote endpoints to turn channel-by-channel feed sampling into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Rednote endpoint catalog — 1 endpoints, 2 documented request parameters, and 1 published response schemas — the same catalog Docs and Playground run against.
1 documented Rednote endpoints, all in the Explore family.
2 request parameters are documented across those Rednote endpoints, 1 of them required — the full input contract is public before you write any integration code.
1 of the 1 Rednote endpoints ship a recorded example response, and 1 carry a documented response schema — you can code against the real JSON before the first request.
Rednote endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
1 hosted MCP tool backs the Rednote endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/rednote/explore
Endpoint catalog
/rednote/exploreReturns one page of the anonymous Rednote (international Xiaohongshu) explore feed as normalized note cards: note id, a public note_url of the form https://www.rednote.com/discovery/item/<id>, the card's short-lived xsec_token, media type, title, cover image, like count, and a public author card. Omit channel_id for the default recommendation feed; use channel_id with an id from the channels list returned by this endpoint for a category feed. The upstream serves one server-rendered page per channel (typically 20-35 cards) and has no credential-free cursor, so there is no pagination. Note detail, user profiles, comments, and search are not available on this anonymous surface: note detail and profiles require the page's guest session, and search requires login, so note_url is a link for a human browser rather than a follow-up API call.
Response notes
- `items` holds public note cards only: `note_id`, `note_url`, `xsec_token`, `type`, `title`, `cover_url`, `liked_count`, and a public `author` card. Description, comments, coordinates, and any account or private field are not part of the anonymous feed. - `note_url` is `https://www.rednote.com/discovery/item/<note_id>` for the card's note id. The separately returned `xsec_token` is a short-lived value: re-run this endpoint for a fresh card and token rather than reusing an old one. Note detail, search, and user profiles are not available on this anonymous surface, so `note_url` is an identifier/link for the caller rather than a promise that a detail call will succeed. - `count` is the number of usable cards in this one response (typically 20 to 35). Cards missing a note id or card body are dropped; if no usable card remains, the endpoint reports an upstream error instead of returning an empty success, so `count: 0` is not a normal result. - `channels` is the channel list the upstream served with this page. Its ids and names are dynamic data from the page rather than a fixed catalog, and the default recommendation feed is reported as `homefeed_recommend`. Cache the list from a response, but do not assume it is stable across sessions. - `channel_id` is the channel the upstream actually served; it may differ from the request when `channel_id` was omitted. - A login or risk-control gate served in place of page state (for example an HTTP 200 challenge page, a redirect to a login or risk page, HTTP 461, or HTTP 403/406/429) is reported as an upstream `503`, not as an empty feed.
MCP tool rednote_explore
Related APIs
Social & Creator Platforms
Build creator intelligence, video research, transcript, and audience-comment workflows without maintaining YouTube scrapers.
Social & Creator Platforms
Turn Twitch's public channel, stream, clip, and team data into structured JSON — live status and viewer counts, top games, clips, VODs, and team rosters — as normalized JSON. Credential-free.
Social & Creator Platforms
Track creator and video activity, discover sounds and LIVE streams, and study public ad creatives through documented TikTok API routes.
How to scrape Rednote
Rednote's official site presents a broad lifestyle feed spanning fashion, food, beauty, television and movies, K-pop, careers, home decor, gaming, travel, fitness, and video. Apple's official listing identifies the developer as Xingin Information Technology (Shanghai) Co., Ltd. and describes a community built around everyday experiences, from cooking and home decor to travel and pets. Crawlora publishes the anonymous explore route: one page of public note cards plus the channel list. On 2026-10-30 the default feed returned 35 cards from channel homefeed_recommend, with 12 channel IDs (Fashion, Food, Beauty, TV & movies, KPOP, Career, Love & life, Home decor, Gaming, Travel, Fitness, Videos). Cards mixed video and normal notes, titles were mostly Chinese, and like counts ran from 0 to 5,201 in the first page of results. There is no cursor, date window, note-detail or comment route in the published surface, and no search or author profile. Preserve each channel and fetch time so recommendations are not mistaken for an archive, and treat cards as user experiences rather than editorial verification.
/rednote/explore accepts an optional channel_id. Read IDs from the response's channels array and pass an exact returned value on a later request. The default response reports channel_id homefeed_recommend, which is not one of the listed IDs (those look like homefeed.travel_v3), so store the served value as returned instead of assuming it is in the list.
The route returns one page of cards (35 on 2026-10-30) and has no page, cursor, since, or date-window input. Record the request time and the channel actually served; two calls minutes apart are two samples, not two pages of one feed.
Each card has note_id, note_url, a separate xsec_token field, type (video or normal), title, cover_url, liked_count, and an author card with user_id, nickname, and avatar. The note_url carries no token. Cover URLs embed a timestamp segment such as 202610301212, so download or re-fetch images rather than storing them as permanent links.
The publisher's visible category mix is useful for classifying returned cards, but those labels are not documented API filters. Build your own topic taxonomy from returned text and channel metadata, and keep the original card fields for auditability.
FAQ
No. The endpoint returns one current explore response and exposes no pagination or historical date window. Save dated snapshots if you need longitudinal observations.
Use an id returned in the endpoint's channels array. The supported list is dynamic, so refresh it rather than hardcoding channel names as IDs.
Not through the published Rednote surface, which is the explore feed. A card gives you note_id, note_url, and counts, which you can store as identifiers, but note detail and comment routes are not offered.
The publisher's official US App Store listing uses the Rednote name and identifies Xingin as developer. Crawlora keeps Rednote and Xiaohongshu as separate API groups because their documented route surfaces differ.