Resolve challenge details and walk the videos behind any TikTok hashtag as paginated JSON - track trends and campaigns programmatically.
If your team plans content around hashtags, you already know the hard part: TikTok does not hand you a clean number. The TikTok Hashtag API gives you that number directly. With a single GET request and your X-Api-Key header you can pull a hashtag's total view count and creator count, search for related tags, and stream the actual videos riding a trend. No headless browser, no scraping fragile HTML, no proxy farm to babysit. You send a request, you get structured JSON back.
This endpoint group is the right fit for social analytics platforms, agency reporting dashboards, trend-discovery tools, and growth teams who want hashtag data they can store, chart and compare over time. Where a documentation page lists fields, this page is about the job to be done: turning a hashtag into a decision. Every example below is a real call against https://api.tikliveapi.com and a trimmed real response.
Send a known challenge ID to /challenge-info-id/ and get back the canonical record for that tag: cha_name, total view_count, user_count (creators who used it), an optional desc, and a cover image URL. Ideal when you already track tags by ID and want a fresh stats snapshot.
Pass a tag spelling to /challenge-info-name/ and resolve it to the same structured record. Use this when your input is human text like a campaign hashtag rather than an internal ID, so you do not have to maintain your own name-to-ID map.
Call /challenge-posts/ with a challenge_id to retrieve the videos currently published under that tag, each with play_count, digg_count, comment_count, share_count, the author and a no-watermark play URL. This is how you see who is actually winning a trend, not just how big it is.
Send any keyword to /search-challenge/ and get a ranked challenge_list of matching hashtags, each with its own view and creator totals. Perfect for discovery: find every variant of a topic and rank them by real reach before you commit to one.
Authenticate with your X-Api-Key header and hit any endpoint with a plain GET request. Here is a live lookup for the hashtag with ID 7551:
curl "https://api.tikliveapi.com/challenge-info-id/?id=7551" \
-H "X-Api-Key: YOUR_API_KEY"
The response is a single JSON object you can store or chart right away (trimmed to the key fields):
{
"id": "7551",
"cha_name": "cat",
"desc": "",
"user_count": 67579511,
"view_count": 1000681687205,
"type": 2,
"cover": "https://p16-sign-va.tiktokcdn.com/..."
}
That single call tells you the cat hashtag has been used by more than 67 million creators and has crossed a trillion views. Swap in your own tag and you have a metric you can log every day. To discover tags instead, point the same request style at /search-challenge/?keyword=cat and read the challenge_list array.
Poll /challenge-info-name/ on a schedule and persist each day's view_count and user_count. Stored over time, those snapshots become the growth curves that headline a client report, an approach we walk through in our guide to tracking trending TikTok hashtags programmatically.
Run a keyword through /search-challenge/ and rank the returned tags by view count to separate a genuinely viral topic from a near-empty lookalike. This is the difference between volume and signal that our hashtag strategy writing covers in depth.
Pull videos under a tag with /challenge-posts/ and study the top performers' play_count and engagement counts to set a realistic bar before you publish. It is the practical side of reading hashtag view counts as signal rather than noise.
Watch a competitor's branded hashtag or your own campaign tag by combining /challenge-info-id/ for reach with /challenge-posts/ for participation, so you can see both how far a campaign spread and who carried it.
Create an account and you get 100 free credits to call every challenge endpoint, no card required. Try the requests live in the in-browser playground, then drop the generated snippet straight into your code. Credits are pay-as-you-go and never expire, so you can build at your own pace.
Every request is a standard GET call that carries your key in an X-Api-Key request header. There is no OAuth flow and no separate token exchange. Sign up to get an API key, then add the header to any call against https://api.tikliveapi.com.
The /search-challenge/ endpoint accepts an optional count parameter that defaults to 10 and maxes out at 30 hashtags per call. The /challenge-posts/ endpoint also accepts count, defaulting to 10 with a maximum of 35 videos per call.
Both /challenge-posts/ and /search-challenge/ return a cursor value and a hasMore flag in the response. To fetch the next page, pass the returned cursor back as the cursor parameter on your next request, and keep going while hasMore stays true.
Use /challenge-info-id/ when you already have a numeric challenge ID, and /challenge-info-name/ when your input is the hashtag text itself. Both return the same record shape, including cha_name, view_count, user_count and cover, so you can pick whichever input you have on hand.
Pricing is pay-as-you-go: you spend credits per API call and your credits never expire. New accounts start with 100 free credits so you can test all four challenge endpoints before buying more.