You have three candidate titles: one is dramatic, another detailed and another natural. An unexplained numerical score will not resolve the choice. Define what a good title must do for this particular note.

Derive criteria from the body

Identify the reader, problem and available evidence. Check audience clarity, specificity and consistency with the content. These are your editorial criteria, not an official ranking formula. Elaborate weighting does not make an exposure forecast valid.

Review reference titles with their content

Search related notes and inspect details to see which titles set accurate expectations. Record why a title works or misleads. Do not translate engagement directly into a title score: images, account context and timing may differ.

Attach an edit to every concern

A table can include candidate, expected takeaway, supporting passage, problem and revision. Replace universal applicability with the actual audience. Remove a savings claim when no comparison supports it. If you use numbers, explain each assessment and preserve unknowns.

Check the final title in context

Read it alongside the opening and cover so the messages do not conflict. Ask another reader to explain the expected content. AI may apply your checklist, while the API supplies reference material; neither creates an authoritative title rating. Keep the review record and observe later performance separately rather than claiming an editorial score proves improved clicks.

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.