You are planning an old-clothes makeover event and want to follow ideas under a TikTok hashtag. A jeans-to-bag video appears yesterday and again today. Counting every returned row would turn that repeat into another discovery.

Resolve the hashtag before comparing days

Search for the hashtag, inspect its details and retain the correct ch_id. Similar spellings may describe different subjects. Query the video list for the same identifier and keep region and sampling choices consistent. Save each observation separately rather than overwriting the earlier list.

Compare identifiers across observations

Record returned video identifiers and lookup times in the first sample. Divide the next sample into previously seen, first observed and unresolved entries. First observed does not mean newly published. Publication claims need a verifiable publication date. When paging, use the returned cursor and record how far you went so a one-page observation is not compared directly with a much larger sample.

Label ideas for the event yourself

After reviewing the content, classify useful references as cutting, mending, decoration or finished-item demonstrations. Add a practical question such as whether the event can provide the necessary sewing tools. Source, first observation date, intended use, repeat status and preparation question are your worksheet columns. These judgments are manual or separately assisted analysis, not automatic event recommendations from the API.

Avoid calling the sample a growth ranking

Different returned lists may reflect sorting, coverage or visibility changes. Describe a small comparison as newly observed references rather than hashtag growth. Scheduling and notifications require your own workflow. The useful handoff is a list of fresh ideas, sources and preparation questions, with the observation limits still visible.

Requests used in this project

Request URL and parameters

GET https://api.trmesh.com/openapi/api/v1/tiktok/app/v3/fetch_hashtag_search_result

Parameter Type Required Meaning
keyword string Yes Keyword
offset integer No Offset
count integer No Number

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/tiktok/app/v3/fetch_hashtag_search_result"
params = {
    "keyword": "Cat"
}
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.