Summary
On xiaohongshu-cli v0.6.4, the notifications command fails for all types with a generic API error, so there's no way to see who liked a comment or who newly followed the account. This is the only data source for that, so the use case is fully blocked.
Environment
- xiaohongshu-cli 0.6.4 (installed as
uv tool, command xhs)
- macOS, cookie-source: Safari
- Account is logged in & valid:
xhs status and xhs whoami return correct profile (authenticated: true)
Repro
$ xhs notifications --type likes
ok: false
error:
code: api_error
message: 'API error: {"code": -1, "success": false}'
Same result for --type mentions and --type connections.
What still works (so it's not auth/cookie)
search, search-user, read, comments, sub-comments, like, comment, follow, reply all return ok: true with this same cookie.
Possibly related
xhs user <user_id> and xhs user-posts <user_id> return the same code -1 error, while search/note endpoints work. These user-profile endpoints may now require an xsec_token that the CLI isn't passing (XHS tightened user-page access). The notifications failure may share the same root cause.
Use case / why it matters
A common workflow is: someone likes your comment or follows you → you open their profile → engage with their related posts. Right now notifications (the only way to get the liker/follower list) is unusable.
Ask
Fix the notifications endpoint (likely a signature/param or xsec_token change on the XHS side), and ideally user / user-posts too. Happy to provide more debug output (-v) if helpful.
Summary
On
xiaohongshu-cliv0.6.4, thenotificationscommand fails for all types with a generic API error, so there's no way to see who liked a comment or who newly followed the account. This is the only data source for that, so the use case is fully blocked.Environment
uv tool, commandxhs)xhs statusandxhs whoamireturn correct profile (authenticated: true)Repro
Same result for
--type mentionsand--type connections.What still works (so it's not auth/cookie)
search,search-user,read,comments,sub-comments,like,comment,follow,replyall returnok: truewith this same cookie.Possibly related
xhs user <user_id>andxhs user-posts <user_id>return the samecode -1error, while search/note endpoints work. These user-profile endpoints may now require anxsec_tokenthat the CLI isn't passing (XHS tightened user-page access). The notifications failure may share the same root cause.Use case / why it matters
A common workflow is: someone likes your comment or follows you → you open their profile → engage with their related posts. Right now
notifications(the only way to get the liker/follower list) is unusable.Ask
Fix the
notificationsendpoint (likely a signature/param orxsec_tokenchange on the XHS side), and ideallyuser/user-poststoo. Happy to provide more debug output (-v) if helpful.