Look Up TikTok Challenge Information by ID
View all TikTok Profiles, Videos & Sounds API endpoints →Retrieve information about a TikTok challenge (hashtag) using the required challenge_id path parameter. The identifier is a string, with 229207 as the documented default. This route targets a known challenge ID rather than accepting a hashtag name or requesting its media feed. No live response was observed for this route, and no response example or field schema was supplied. Its returned field names and available metrics remain unverified; do not assume that the separate hashtag-name lookup's data.ch_info fields also appear here. Inspect the actual response before defining metadata mappings or counter calculations. This lookup does not establish historical trends or an exhaustive collection of challenge videos.
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-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tiktok/challenge-data-by-id?key=<API_KEY>&challenge_id=229207'
Query Result
Use Cases
- Revisit a saved campaign challenge_id to capture the metadata returned on each review date.
- Attach the requested challenge_id and a locally recorded fetch timestamp to a hashtag archive so its metadata snapshots remain traceable.
- Check a shortlist of stored hashtag identifiers before choosing separate challenge-feed requests for editorial sampling.
- Validate the ID-lookup response contract in an ingestion pipeline without copying field mappings from the hashtag-name lookup.
Frequently asked questions
What should I send as challenge_id?
Send an existing TikTok challenge identifier as a string. The documented default is 229207. Keep the value as text even if it contains only digits.
Can I pass a hashtag name instead of an ID?
This route is documented for a challenge ID, not a hashtag name. Use the separate challenge-name lookup when your starting point is a name such as fyp.
Which response fields are confirmed for the ID lookup?
None were confirmed for this route: there was no observed live response and no supplied response example or field schema. Validate the actual payload before relying on names, identifiers, counters or nested objects. The name-lookup response is not evidence of this route's schema.
Should I use this lookup to collect challenge videos or historical statistics?
Its documented purpose is challenge information. Use the separate challenge feed route to request associated media, and do not treat either route as a guaranteed full historical export or a source of historical trends.