What this API is and who it is for
The TikTok API is a third-party REST API that wraps TikTok's public-facing data into a consistent, developer-friendly interface. It is aimed at developers who need to pull profile stats, video details, comment sentiment, trending content or search results from TikTok without having to deal with TikTok's official — and notoriously restrictive — developer program. Social media analytics tools, influencer marketing platforms, content research dashboards and competitive intelligence products are the obvious primary consumers.
All 60 endpoints use simple GET requests, which keeps integration straightforward. You pass identifiers (usernames, numeric user IDs, video URLs, hashtag names, music IDs) as query parameters and receive structured JSON in return.
Endpoint walkthrough
The API groups its 60 endpoints into logical categories. Here is what each area actually gives you:
Profile
Five endpoints handle user identity resolution and profile data. /getUserSecUid translates a human-readable username into the internal secUid token that most other user-scoped endpoints require — this is often the first call in any workflow. /getProfile and /getUserComplete return rich profile objects covering bio, follower/following counts, total likes, video counts, avatar URL and verified status. /getUserInfoByID serves the same purpose when you already have a numeric ID rather than a username. /getBusinessInfo surfaces commerce-specific fields like bio links and category tags that are absent from standard profile responses.
Video
Six endpoints cover video data. /getVideoInfo returns the full metadata object for any video given its URL — stats, author details, music info and engagement figures. /getVideoHD appends HD download links to that payload. /getDownloadVideo specifically returns a watermark-free download URL, which is relevant for content archiving use cases. /getVideoSubtitles handles caption retrieval, with optional full-text fetch per language. /getVideoMeta emphasises SEO and structured data alongside hashtags and engagement, making it useful for content auditing tools.
Comments
Four endpoints address comments. /getVideoComments and /getCommentsExtended both return paginated comment lists, with the extended variant offering configurable page sizes and additional fields. /getVideoCommentReplies drills into individual comment threads. The most analytically interesting endpoint here is /getCommentInsights, which returns sentiment distribution, average likes and replies per comment, and top commenter identification — essentially pre-computed comment analytics rather than raw data.
Search
Nine endpoints cover search across multiple content types: general mixed results, videos by keyword, users, music, live streams and hashtags. /getSearchSigner acts as an advanced gateway supporting type-filtered queries. /getVideosByKeyword adds pagination, which is important for bulk data collection.
Hashtag
Five endpoints expose hashtag and challenge data. Beyond basic challenge details (view counts, description, cover image), /getHashtagCorrelation returns related hashtags that co-appear frequently — a useful signal for content strategy tooling. /getHashtagVideosSorted adds sorting by relevance, likes or recency.
Music
Four endpoints handle sound-level data: music metadata, download URLs for audio tracks, and reverse lookups to find all videos using a given sound.
Feed and trending
Four endpoints return algorithmically curated feeds. /getTrendingVideos returns globally trending content; /getRegionTrending scopes it to a country. /getFYPFeed mimics the For You Page for a chosen region, and /getExploreFeed returns Explore page content by category.
User content
Three endpoints focus on derivative content: duets, stitches and a user's own video feed with pagination.
Pricing
| Plan | Monthly price | Included requests | Rate limit | Overage per request |
|---|---|---|---|---|
| BASIC | $0 | 80 | 1,000 / hour | — |
| PRO | $39 | 1,000,000 | 60 / minute | $0.0001 |
| ULTRA | $89 | 2,500,000 | 150 / minute | $0.0001 |
| MEGA | $149 | 5,000,000 | 240 / minute | — |
The BASIC tier's 80-request monthly cap is best understood as a test environment, not a production budget. At one request per profile lookup, 80 calls barely covers a small proof-of-concept. Any real integration — even a personal project that checks a handful of accounts daily — will exhaust BASIC within days and requires upgrading to PRO.
PRO at $39/month gives you one million calls and a per-minute rate limit of 60, which translates to roughly 2.6 million requests per day at sustained throughput (capped by the monthly quota well before that). Overage on PRO is $0.0001 per request, so exceeding the quota by 500,000 calls adds $50 to the bill — worth modelling before you go live. ULTRA doubles the included quota and the rate limit for $89, and MEGA doubles it again to five million requests at $149 with no overage pricing listed, suggesting it is intended as a hard-cap plan.
For teams running daily analytics pipelines across thousands of accounts or videos, ULTRA or MEGA will be the realistic tiers. Social listening products ingesting real-time search or comment data at scale should benchmark against the 240/minute ceiling on MEGA before committing.
Practical use cases
- Influencer analytics platforms: combine
/getProfile,/getUserVideosand/getCommentInsightsto build per-creator engagement dashboards. - Trend monitoring: poll
/getTrendingVideosand/getRegionTrendingon a schedule to track content virality across markets. - Competitor research tools: use search endpoints to surface competitor brand mentions and hashtag adoption.
- Content archiving: chain
/getVideoInfowith/getDownloadVideoor/getVideoSubtitlesfor transcript-based content analysis. - Hashtag strategy: use
/getHashtagCorrelationto surface related tags and inform campaign planning.
Limitations and things to check before integrating
Average latency of 1,338 ms is on the slower side. For synchronous, user-facing features this matters — building an interface that blocks on a real-time TikTok lookup will feel sluggish. Batch or background processing architectures are better suited. Consider caching responses aggressively, particularly for profile and hashtag data that does not change by the second.
The rate limits shift significantly between plans. BASIC's 1,000 per hour sounds generous but the 80-request monthly total is the real constraint. PRO's 60 requests per minute is the first tier where sustained workloads become feasible. If your architecture involves burst requests — for example, a user triggering many parallel lookups — test whether the per-minute ceilings cause visible queuing.
Because this is a third-party API that wraps TikTok's public data, its continued availability depends on TikTok's own platform changes. Endpoints can break if TikTok alters its internal API structure, even though the 100% reported success rate is currently excellent. Build appropriate error handling and monitoring into your integration from day one.
Getting started
Subscribe on the marketplace, obtain your API key, and make a first call to /getUserSecUid with a known TikTok username to validate connectivity. From there, the secUid value unlocks most of the profile and content endpoints. With only 80 requests on the free tier, map out which endpoints your core workflow requires before running exploratory calls, so you can assess fit before upgrading to PRO.
