Tiktok Video Feature Summary API: Review & Developer Guide

What the API does and who it is for

TikTok does not offer a fully open public API for video data, which has created a thriving market for third-party scrapers and data proxies. Tiktok Video Feature Summary fills that gap by providing structured JSON access to most of the objects a developer would want: videos (with HD, watermark-free download URLs), user accounts, follower graphs, comments, music tracks, playlists, collections, and trending hashtag feeds.

The API targets a fairly broad developer audience. Social media monitoring tools, influencer analytics platforms, content aggregators, academic researchers studying short-form video trends, and developers building recommendation engines around TikTok content are all natural fits. Because the free tier is tight (100 requests per month), it is primarily a paid-tier product for production workloads, but the free plan is enough to prototype integrations and validate data shapes before committing to a subscription.

Endpoint walkthrough

The 23 endpoints are organized into six functional groups plus a root video endpoint.

Video resolution and metadata

The root GET / endpoint is arguably the most distinctive one: given a TikTok video URL, it returns the full video record — HD video address without watermark, author profile, background music, view count, like count, and comment count. For any use case where you need to display or archive TikTok content cleanly, this single endpoint does heavy lifting.

GET /feed/search returns a list of videos matching a keyword, and GET /feed/list returns a regional feed — useful for trend tracking per geography. The GET /region endpoint supplies the list of valid region codes to use as parameters in feed queries.

User and social graph endpoints

The Users group covers the full user object lifecycle:

• GET /user/info resolves either a unique_id (username) or a numeric user_id to a detailed profile.
• GET /user/posts fetches a user's public video feed.
• GET /user/favorite retrieves a user's favorited videos.
• GET /user/followers and GET /user/following expose the social graph — useful for influencer-mapping features.
• GET /user/search finds users by keyword.

The dual-key design (unique_id or user_id) is a small but practical convenience: you can start with a username from a marketing brief and pivot to a stable numeric ID for subsequent calls without an extra lookup round-trip.

Comments

GET /comment/list returns top-level comments on a video, and GET /comment/reply fetches replies to a specific comment. This two-level nesting matches TikTok's own comment structure, which means you can reconstruct a full comment thread without any client-side heuristics.

Music, playlists, and collections

GET /music/info resolves a music track ID to its metadata — useful for music trend analysis or rights-awareness tooling. The Playlist and Collection groups each follow the same pattern: list all entities for a user, fetch metadata for one, and fetch the constituent videos. This symmetry makes the data model easy to reason about.

Hashtags

GET /challenge/search, GET /challenge/info, and GET /challenge/posts cover hashtag (TikTok calls them "challenges") discovery, detail lookup, and associated video listing. These three endpoints together are sufficient to build a basic hashtag trend monitor.

Pricing breakdown

The API follows a tiered freemium model. All paid tiers are billed monthly, and the PRO plan adds per-request overage billing once the monthly cap is exhausted.

A few observations worth making before you choose a plan:

BASIC is genuinely only useful for evaluation. At 100 requests total in a month, you cannot support even a minimal production feature.

PRO at $9.80 offers 600,000 requests — enough for moderate workloads — but the overage pricing ($0.0001 per request) means a spike to 1 million extra requests would cost an additional $100. If your traffic is unpredictable, the fixed-cost ULTRA plan may be safer.

ULTRA at $32.80 with 3 million requests and a 30 req/s rate limit is the recommended tier for most production applications. The per-request effective cost works out to roughly $0.000011, well below the PRO overage rate.

MEGA at $299 is for high-volume data pipelines — crawlers, large-scale analytics platforms, or multi-tenant SaaS products. The 50 req/s ceiling and ~10.5 million monthly requests leave substantial headroom.

If your volume exceeds the MEGA tier, the provider mentions the option to negotiate a custom package directly.

Practical use cases

• Influencer analytics dashboards: Combine /user/info, /user/posts, /user/followers, and /user/following to compute engagement rates, follower growth, and content cadence for a given creator.
• Trend monitoring: Poll /feed/search and /challenge/posts on a schedule to surface rising hashtags and viral videos in specific regions using /feed/list with targeted region codes.
• Content archiving: Use the root / endpoint to retrieve watermark-free HD video URLs for legitimate archival or republishing workflows (subject to your platform's terms).
• Competitive research tools: Map comment sentiment with /comment/list and /comment/reply across a competitor's video catalog.
• Music intelligence: Track which audio tracks are appearing across trending videos by cross-referencing /music/info results with feed data.

Limitations and things to check before integrating

Latency: The 910 ms average latency is on the higher side for a user-facing feature. If you are rendering TikTok data in a UI synchronously, consider caching responses aggressively or pre-fetching on a schedule rather than making live API calls per page load.

Rate limits on lower tiers: The BASIC plan has no documented rate limit, but with only 100 requests available in a month the ceiling is effectively the quota itself. The PRO plan's 10 req/s limit is adequate for sequential crawling but could bottleneck a concurrent multi-threaded scraper.

No ULTRA overage: Unlike PRO, the ULTRA plan does not offer overage billing. If you exceed 3 million requests in a month, you would need to upgrade or pause requests — something worth accounting for in application logic.

Third-party data source: This is not an official TikTok product. Availability is subject to any changes TikTok makes to its underlying platform, and data completeness depends on what is publicly accessible. Build defensive error handling around all responses and do not assume field stability across API updates.

Limited music metadata: Only a single /music/info endpoint is available; there is no bulk music lookup or music search, which may require multiple serial calls if you are processing a large video dataset.

Getting started

Subscribe on the marketplace to activate your BASIC key immediately — no credit card is required for the free tier. With 100 requests, a sensible onboarding flow is:

1. Call GET /user/info with a known TikTok username to confirm authentication and inspect the user object schema.
2. Pass the same user's numeric ID to GET /user/posts and review the video array.
3. Take one video URL from that response and pass it to GET / to verify you can retrieve HD video metadata end-to-end.

Once you have validated the data shapes against your application's needs, estimate your monthly request volume and choose the appropriate paid tier before going to production.