What TikTok Scraper does and who it is for
TikTok Scraper is a third-party REST API that sits in front of TikTok's platform and surfaces public data in a structured, developer-friendly format. Rather than wrestling with TikTok's official (and heavily restricted) developer program, teams use APIs like this to pull profile data, video metadata, comment threads, hashtag analytics, and more without managing browser automation or reverse-engineered clients themselves.
The typical adopters are social media analytics tools, influencer marketing platforms, content aggregators, research teams studying short-form video trends, and app developers who want to embed TikTok content or statistics in their products. With nearly 6,000 subscribers and a near-perfect popularity score of 9.9 out of 10, TikTok Scraper has established a clear track record in the marketplace.
One practical number to keep in mind before integrating: the average response latency sits at 4,134 ms and the average success rate is 93%. That means roughly one in fourteen requests will fail, and round-trip times are measured in seconds rather than milliseconds. This is broadly typical for scraper-backed APIs — the provider is fetching live data from TikTok on your behalf — but it has real design implications. Plan for retry logic, don't put these calls in a synchronous user-facing critical path, and cache aggressively wherever your use case allows.
Endpoint walkthrough
TikTok Scraper offers 16 GET endpoints grouped naturally by resource type.
User data
/user/info— Returns profile-level data for a given account: follower counts, following counts, video count, bio, verification status, and similar fields./user/videosand/user/videos_v2— Lists a user's public videos. The_v2variant is described as "full," suggesting a richer response payload; worth testing both to see which fields your integration needs./user/follower— Returns the followers list for a user./user/following— Returns the accounts a user follows./user/likes— Returns the videos a user has liked (only where the account has made likes public)./user/playlist— Returns a user's public playlists.
Video data
/video/infoand/video/info_v2— Two versions of the video detail endpoint. When an API maintains a legacy and a current version simultaneously, it usually means the v2 response schema changed in a breaking way; check which fields each returns before committing to one./video/no_watermark— Returns a download URL or stream for the video without the TikTok watermark overlay. This is the endpoint most likely to attract platform policy scrutiny, so review TikTok's terms and your jurisdiction's copyright rules before building around it./video/comments— Returns comments on a specific video./video/comment_reply— Returns replies to a specific comment, enabling full thread reconstruction.
Hashtag and music data
/hashtag/info— Returns metadata about a hashtag or challenge: view count, video count, and description./hashtag/videos— Returns videos associated with a hashtag, useful for trend monitoring and content discovery pipelines./music/info— Returns metadata about a sound or music track used on TikTok./music/videos— Returns videos that use a specific sound, enabling trend tracking by audio.
Pricing breakdown
TikTok Scraper uses a tiered billing model with daily request quotas. All limits are per calendar day.
| Plan | Price | Daily requests | Overage |
|---|---|---|---|
| BASIC | $0 / month | 20 | — |
| PRO | $5 / month | 1,000 | — |
| ULTRA | $20 / month | 5,000 | — |
| MEGA | $100 / month | 50,000 | $0.0001 per request |
The free BASIC tier's 20 daily requests is genuinely tight — enough for a quick proof of concept or a personal project that runs a handful of lookups per day, but not enough for any automated pipeline. A single user profile fetch plus their video list could consume half your daily allowance in one operation.
PRO at $5/month and 1,000 daily requests is the realistic entry point for a small production integration. At $0.005 per request effective cost, it is inexpensive for low-volume social listening or a small analytics dashboard.
ULTRA and MEGA scale linearly in price relative to quota. MEGA's overage rate of $0.0001 per request ($0.10 per 1,000 requests) makes burst usage affordable. The provider also mentions a custom plan option via Telegram for requirements beyond MEGA.
Practical use cases
Influencer analytics: Combine /user/info, /user/videos_v2, and /user/follower to build engagement-rate calculators and growth-trend charts for creator profiles.
Hashtag trend tracking: Poll /hashtag/info and /hashtag/videos on a schedule to surface emerging trends before they peak. At 1,000 daily requests on PRO, you could monitor around 30–40 hashtags per hour with room to spare.
Audio trend discovery: /music/videos lets you see which sounds are spreading, useful for brands and music marketers tracking audio virality.
Comment sentiment analysis: /video/comments plus /video/comment_reply gives you full comment thread data to feed into NLP pipelines for audience sentiment research.
Content archiving: /video/no_watermark combined with /video/info_v2 lets you fetch clean video files alongside structured metadata — relevant for research datasets or archival purposes, subject to applicable terms.
Limitations and things to check before integrating
Success rate: A 93% success rate means you must implement retry logic. For any pipeline that needs guaranteed delivery, build a queue with exponential backoff.
Latency: At roughly 4 seconds average, TikTok Scraper is unsuitable for real-time user-facing features. Design for asynchronous delivery: trigger the request, store the job, return results when ready.
Daily vs. monthly quotas: All plans cap by day, not by month. A burst that exhausts your daily 1,000 requests at noon leaves you dark until midnight UTC. Plan your request scheduling accordingly.
Platform terms: Third-party scraping APIs operate in a legally ambiguous space relative to TikTok's Terms of Service. Scraper availability can change if TikTok alters its underlying API or bot-detection systems. Build your integration so you can swap data sources without a full rewrite.
No authentication details disclosed: The fact sheet does not specify the auth mechanism (API key, OAuth, etc.). Confirm this during your marketplace onboarding before writing integration code.
Getting started
Subscribe through the marketplace (BASIC is free with no credit card required for testing), then explore the endpoints against a few known TikTok usernames and video URLs to verify the response shapes match your expected schema. Given the dual versioning on both /video/info and /user/videos, run both variants side by side early so you pick the richer one before building your data models. Set up a simple retry wrapper from day one — with a 93% success rate you will see failures in testing, and having the retry layer in place before production will save a painful refactor later.
