What is xsec_token on Xiaohongshu?
xsec_token is an access token Xiaohongshu (RedNote) puts on note and profile links, usually beside xsec_source. With DataXAPI you do not handle it: the note endpoints take the bare note ID, and every search result's url already carries its token. DataXAPI reads Xiaohongshu (RedNote) with 21 endpoints, from $0.0200 a call; a failed call is not charged.
What it is and where you see it
It is a query parameter on a note's web link and on a profile link: https://www.xiaohongshu.com/explore/0123456789abcdef01234567?xsec_token=ABx1y2z3&xsec_source=pc_search (a made-up example). The 24 characters in the path are the note ID; the token and xsec_source follow it.
Xiaohongshu has published nothing on what the token is for. As public open-source tools describe it, a note link should carry it, and it is a token that comes with search results; one such project's issue reports a note that failed to load with the message 访问链接异常 (abnormal access link).
What DataXAPI does with it
xiaohongshu.notes.search writes each result's url the way the app shares a note, /discovery/item/<id> with its xsec_token, so the link opens for a person. DataXAPI has recorded a token on every result of a page.
The note, comment and profile endpoints take the 24-character ID as id, or a link pasted as it is as url, with or without the token: the ID is read from the link's path, and the token says nothing about which note it is.
Endpoints
Each with its price; every page has the parameters, the fields and a recorded response.
Sources
What this page says of other services is from their own pages and documents, read on 2026-10-29. Prices and features change: check the source before you decide.