Large creators have resources you cannot easily reproduce. You would rather learn from accounts closer to your own scale. Define what smaller means and what performance you are comparing before selecting examples.
Set explicit comparison conditions
Choose a follower range, topic and publication window. These are your research criteria, not an official platform label. Search relevant notes and retrieve the appropriate details. A modest-looking cover does not prove a small account.
Check author and note information together
Record the lookup time for available follower data. A current count is not necessarily the count when the note was published, so it cannot establish a historical growth claim. Missing values are unknown, not zero. Compare only available compatible metrics without inventing views or conversions.
Study affordable explanatory choices
Read how each note introduces a problem, presents evidence and states limits. Your table can contain source, author-data date, topic, explanatory choice, technique you could try and unknown conditions. A dimension comparison image may be useful, but the sample alone does not prove it caused engagement.
Choose one feasible experiment
Apply a relevant technique using your own materials. AI can compare structures but must not reconstruct historical follower counts or promise equivalent results. Deliver a bounded reference list and a practical production plan. If no candidates meet the criteria, report that gap rather than silently changing the definition.
Requests used in this project
- Search notes:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/search_notes · Documentation
- Get image note detail:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_image_note_detail · Documentation
- Get video note detail:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_video_note_detail · Documentation
- Get user info:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_user_info · Documentation
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/search_notes
| Parameter | Type | Required | Meaning |
|---|---|---|---|
keyword |
string | Yes | Search keyword |
page |
integer | No | Page number, start from 1 |
sort_type |
string | No | Sort type |
note_type |
string | No | Note type: 不限, 视频笔记, 普通笔记, 直播笔记 |
time_filter |
string | No | Time filter: 不限, 一天内, 一周内, 半年内 |
search_id |
string | No | Search ID for pagination |
search_session_id |
string | No | Search session ID for pagination |
source |
string | No | Source |
ai_mode |
integer | No | AI mode: 0=off, 1=on |
Run the Python example
Install requests and set TRMESH_API_TOKEN in your environment. Replace the sample identifiers with the public object you intend to inspect. Example IDs may no longer be available.
import os
import requests
# Read your own developer key from the server environment.
url = "https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/search_notes"
params = {
"keyword": "美食推荐",
"page": "1",
"sort_type": "general",
"note_type": "不限",
"time_filter": "不限",
"source": "explore_feed",
"ai_mode": "0"
}
response = requests.get(
url, params=params, timeout=30,
headers={"Authorization": f"Bearer {os.environ['TRMESH_API_TOKEN']}"},
)
response.raise_for_status()
payload = response.json()
print(payload) # Inspect the actual response before mapping fields
Endpoint documentation · Free profile tool
API calls use your TRMesh account allowance. Check the endpoint price before running a script.

