Resolve a TikTok Hashtag Name to Challenge Metadata
View all TikTok Profiles, Videos & Sounds API endpoints →Retrieve challenge (hashtag) information using the required challenge_name string path parameter. Despite the operation's keyword label, this is documented as a name lookup, not a free-text search returning multiple matching hashtags. The documented example and default are fyp. In the supplied successful probe for fyp, HTTP 200 returned status=ok and data.status_code=0. The observed data.ch_info object contained cha_name, the returned hashtag name; cid, the challenge identifier; user_count, a reported usage-related counter; and view_count, a reported view counter. That probe returned cha_name=fyp and cid=229207, with nonzero user_count and view_count values and share information whose exact nested fields were not specified. These fields are observed in one probe, not a guaranteed schema for every name; no separate response example or field schema was supplied. Retain both the submitted name and returned cid when connecting to challenge-ID lookups or media feeds. Record counters as timestamped reported snapshots, not unique people, deduplicated reach, growth rates or a historical trend.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/tiktok/challenge-data-by-keyword API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tiktok/challenge-data-by-keyword?key=<API_KEY>&challenge_name=fyp'
Query Result
Use Cases
- Resolve an analyst's known hashtag name to the returned cid before constructing a separate challenge-ID workflow.
- Create a timestamped hashtag reference card using the observed cha_name, cid, user_count and view_count fields when present.
- Record both the submitted challenge_name and returned cha_name to make campaign hashtag references auditable.
- Capture the observed status and data.status_code alongside a name-lookup result so a collector can distinguish reported success from missing expected metadata.
Frequently asked questions
Is challenge_name a hashtag name or a broad keyword search?
It is documented as the name of a challenge or hashtag. The example is fyp. A multi-result keyword search, fuzzy matching and support for arbitrary text phrases are not documented for this route.
How can I obtain a challenge ID from a hashtag name?
In the supplied successful fyp probe, data.ch_info.cid was 229207 and data.ch_info.cha_name was fyp. Validate those fields in your actual response, retain the returned identifier, and use it with a separate challenge-ID lookup or challenge feed request.
Which metadata fields were actually observed?
The fyp probe returned status=ok, data.status_code=0 and data.ch_info fields cha_name, cid, user_count and view_count, plus share information with unspecified nested fields. This single observation does not guarantee that every lookup returns the same fields. No separate response example was supplied.
Do user_count and view_count measure unique reach or growth?
Their exact counting definitions are not established by the supplied evidence. Treat them as reported counters captured at a particular time, not unique people, deduplicated reach or growth rates. One response is not a historical time series.