You save a few references each day, but the same popular note appears four times by the weekend. Adding its observed interaction counts would exaggerate its presence. Reconcile duplicates and timing before interpreting the week.

Define the weekly scope

Choose dates and a timezone, distinguishing notes published this week from notes observed this week. Use documented search settings and verify timing in available details. Keep uncertain entries separate and do not call the result an official platform ranking.

Merge observations by note identifier

Create one main record per note, retaining separate observation times beneath it. Visible interaction counts are commonly cumulative observations, not daily quantities to add. If comparing two observations, preserve their interval and missing data rather than treating an unavailable value as zero.

Group by the problem addressed

Inspect image or video details and identify the reader question. Current author information is context, not a historical follower record. Your weekly table can contain source, theme, first observation, observations during the week, useful expression and gaps. AI can group topics but cannot establish platform-wide shares or causes of growth.

Produce a plan for next week

Select questions worth investigating and the evidence each needs. A clear explanation with missing limitations may suggest a real test, not a copied title. Narrow conclusions when coverage is small. The deliverable should explain what was repeatedly observed, what came from distinct sources and what you will investigate next.

Requests used in this project

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.