You want to compare rental-storage ideas from several creators without losing sources or repeatedly saving the same note. Build an author-to-note index instead of an unlabelled screenshot collection.
Verify candidates through their actual work
Search users, retrieve profiles and inspect homepages. A storage-related name does not establish the account's current focus. Record the identifier, source and reason for inclusion. Do not merge similar names or assume the first search result is the best match.
Retain progress for each account
Retrieve posted notes using actual cursors for the intended coverage. Deduplicate known note identifiers across pages and state the observed range. Pagination does not justify claiming a complete historical archive when some content remains uncollected.
Inspect image and video notes appropriately
Use the corresponding detail endpoint for selected notes. Identify the space and problem addressed. Useful columns include author source, note link, room type, limitations, material status and reading notes. Dimensions embedded in images and actions shown in videos require inspection, not inference from a cover.
Keep the collection useful for comparison
Group similar methods while retaining separate sources and differences in rental constraints, surfaces and budget. AI can classify verified material but should not add unstated dimensions or supplies. Add newly observed relevant notes during updates. The result is a manageable reading index, not a complete account download or permanent content warehouse.
Requests used in this project
- Search users:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/search_users · Documentation
- Get user info:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_user_info · Documentation
- Get user posted notes:https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/get_user_posted_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
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/xiaohongshu/app_v2/search_users
| Parameter | Type | Required | Meaning |
|---|---|---|---|
keyword |
string | Yes | Search keyword |
page |
integer | No | Page number, start from 1 |
search_id |
string | No | Search ID for pagination |
source |
string | No | Source |
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_users"
params = {
"keyword": "美食博主",
"page": "1",
"source": "explore_feed"
}
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.

