One note says a seaside destination is walkable; another says a car is essential. Both may describe valid experiences with different accommodation, weather and companions. Compare those conditions before copying a route.
Search around practical needs
Separate arrival, accommodation surroundings, food and rainy-day alternatives, using specific place names. Review a small relevant sample and preserve search settings. One beach does not describe an entire city's access, and peak-season experiences may not fit a quieter weekend.
Find the circumstances behind the experience
Retrieve image or video details appropriately and check timing, route, companions and transport. Leave missing context unknown. A sunny photograph does not establish full-day weather, and convenient may mean driving rather than walking with children and luggage.
Explain conflicting advice in a table
Include source, timing, accommodation area, transport, applicable parts and open questions. AI may organize differences but must not invent current services, prices or opening times. Verify those separately through appropriate current official information before departure.
Leave optional parts in the itinerary
Choose essential and cancelable activities around your family's interests and energy, with a weather alternative. A creator's budget is not a promise about your costs. The APIs do not book rooms, assess sea conditions or buy tickets. Deliver a preparation plan that distinguishes supported arrangements from items still needing confirmation.
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
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.

