Xiaohongshu (RedNote) Scraper & API | EveryInfra

EveryInfra Xiaohongshu (RedNote) API scrapes notes, posts, comments, user profiles, followers, and product data using 12 dedicated App actions.

No official affiliation.

Active Actions

12 active App actions only:

• search: Search notes/posts by keyword
• note: Get a specific note by ID
• comments: Get comments for a note
• sub_comments: Get sub-comments
• user_post: Get posts by user
• user_info: Get user information
• user_followers: Get followers of a user
• user_search: Search for users
• topic: Get notes by topic
• product_search: Search products
• product_detail: Get product details
• product_review: Get product reviews

Usage

Both flat parameters and a params object are accepted. If the action field is omitted, search is used.

Flat example:

{"action":"search","keyword":"coffee","page_size":20}

Nested example:

{"action":"search","params":{"keyword":"coffee","page_size":20}}

For search only, num is accepted as an alias of page_size. For comments and sub_comments, num keeps its existing meaning as items per page.

If both shapes provide the same canonical key, equal values are accepted and conflicting values fail. num and page_size count as the same canonical key for search.

Each run requests just one page, with manual pagination. Requested page_size/num is NOT a strict result cap: a source page may contain more or fewer rows. No automatic retries or pagination.

Invalid input does not consume a trial or call the data service.

The Form has keyword coffee as an example only; when switching operations, clear non-applicable example fields. Blank fields for other operations are ignored; unknown fields are still rejected.

Trial Policy

The first 3 accepted data-request attempts per Apify account are free of result-event charges, shared across all EveryInfra Actors using this policy; no daily reset and no per-Actor reset. Each run makes one source request only. A reserved trial counts even when the request is empty or fails; invalid input is rejected before reservation. After 3 trials a paid Apify plan is required and normal event pricing applies. Retries/restarts cannot create another free attempt. No automatic retries or pagination.

Pricing

Action	Billing unit	USD per unit
note	request	0.013
comments	request	0.013
sub_comments	request	0.013
user_info	request	0.013
user_followers	request	0.013
search	record	0.0028
user_post	record	0.0028
topic	record	0.0028
user_search	record	0.004
product_search	record	0.0032
product_detail	request	0.015
product_review	record	0.004

No startup charge or extra default-dataset event charge. Empty data and source errors before delivery result in no charge. Budget must cover complete returned page or the request fails before any result delivery or charge. No fee for nonexistent records. An interrupted delivery may require inspection of dataset/charges before retry.

Note: Embedded review replies included, not extra charged. Creator covers platform running costs. Empty or failed requests before delivery have no result-event charge. Paid run budget must cover a complete returned page; otherwise no delivery or charge. Separate paid runs independent; dedupe within one page.

Pagination and Inputs

note_id, user_id, comment_id and last_note_id must be 24-character hexadecimal strings.

note.node_type defaults to images. A video node_type can cause the source to return the wrong note; the wrapper rejects a mismatch. Use the default first.

search, user_search, and product_search pages start at 1. product_review pages start at 0. comments, sub_comments, user_post, and user_followers use a cursor. For comments and sub_comments, use output pagination.next_cursor when it is supplied.

First page of action topic requires only topic_id. To request a later page, provide last_note_ct, last_note_id and cursor_score from the same returned note. The topic_id in the topic URL can differ from its display tag id.

num and page_size accept 1–100, but the source may ignore them. A search with page_size 1 returned 20 records. A comments sample with num 15 returned 15. sub_comments with default 10 returned 5.

Output Format

• OUTPUT holds full response page plus pagination
• request-priced dataset has one page row
• per-record dataset has rows {action,record_id,data}
• product_search and product_detail have nested data.module.data cards
• product_review uses data.reviews
• Only product cards count for product_search

Parameter reference

Action	Required parameters	Optional parameters and defaults
search	keyword	page=1, page_size=20, sort="综合", note_type="不限", note_range="不限", search_id="", session_id="", note_time="不限"
note	note_id	node_type="images"
comments	note_id	num=15, sort="默认", cursor=""
sub_comments	note_id, comment_id	num=10, cursor=""
user_post	user_id	cursor=""
user_info	user_id	—
user_followers	user_id	cursor=""
user_search	keyword	page=1, fans_count="all", user_type="all"
topic	topic_id	sort="最新", last_note_ct="", last_note_id="", cursor_score=""
product_search	keyword	page=1, sort="综合", filters_tags=[]
product_detail	sku_id	—
product_review	new_sku_id	sort_strategy_type="综合", page=0

Allowed enum values

• search.sort: 综合, 最新, 最多点赞, 最多评论, 最多收藏, 英文优先
• search.note_type: 不限, 视频笔记, 普通笔记, 直播笔记
• search.note_range: 不限, 已看过, 未看过, 已关注
• search.note_time: 不限, 一天内, 一周内, 一个月内, 一年内
• note.node_type: images, video
• comments.sort: 默认, 最新, 最多点赞
• user_search.user_type: all, regular_user, personal_verification, business_verification
• topic.sort: 最新, 最热
• product_search.sort: 综合, 销量, 价格升序, 价格降序
• product_review.sort_strategy_type: 综合, 最新

Support

Support via Apify Issues. See EveryInfra profile at https://apify.com/blushing_parachute