TokApi Mobile Version: TikTok Scraping API Review

What TokApi mobile version does and who it's for

TokApi - mobile version is an unofficial scraping layer over TikTok's internal mobile API. Instead of reverse-engineering TikTok's app traffic yourself — a process that requires keeping up with frequent app updates, managing device fingerprints, and handling rate limiting — you delegate that complexity to TokApi and call clean REST endpoints. The service mimics the mobile client (including support for multiple app versions such as 28.1.1, 20.7.5, and 28.9.3) so the responses you receive reflect what a real TikTok mobile user would see.

The primary audience is developers building analytics dashboards, social media monitoring tools, content aggregators, or research pipelines that need TikTok data without an official API. With a popularity score of 9.9 out of 10 and more than 11,300 marketplace subscribers, it is among the most widely used TikTok data APIs available.

One important caveat worth acknowledging upfront: this is an unofficial API. It does not have TikTok's endorsement, and your usage is subject to TikTok's terms of service. Evaluate that risk before integrating it into a production product.

Endpoint coverage

TokApi exposes 82 endpoints in total. The 40 documented in the public listing already span a wide surface area. Here is how the major functional groups break down:

User data

• Retrieve a user profile by numeric ID (GET /v1/user/{user_id}) or by username (GET /v1/user/{username} and /v1/user/username/{username})
• Fetch a user's full video feed, liked video feed, and playlists
• Get all videos belonging to a specific playlist by playlist ID

Posts and video discovery

• Look up a specific video by its ID (GET /v1/post/{post_id}) or resolve a short or full TikTok URL directly (GET /v1/post), which is useful when you have a vm.tiktok.com share link rather than a raw post ID
• Pull a user's public video feed by user ID (GET /v1/post/user/{user_id}/posts) or via alternative IDs (GET /v1/post/user/posts)
• Retrieve comments for any video (GET /v1/post/{post_id}/comments)
• Search for videos by text query (GET /v1/search/post) or by hashtag ID (GET /v1/hashtag/{hashtag_id})

Live streams

• Search live streams by keyword (GET /v1/search/live)
• Browse the live feed and get detailed live session info
• Access live ranking lists and ranking details

Effects and music

• Fetch effect (sticker) metadata by ID or batch-fetch multiple effects at once
• Retrieve all videos that use a specific effect (GET /v1/sticker/posts/{sticker_id})
• Look up music track metadata by ID (GET /v1/music/{music_id})

TikTok Shop

• Browse the shop homepage, flash sales, and new-user exclusive deals
• Search products by text and fetch recommended products by category

Service / utility

• POST /v1/service/sign generates signed request headers for direct TikTok API calls across three supported app versions, which is useful if you want to make lower-level requests yourself.
• POST /v1/service/device/generate creates and registers a virtual device, likely needed for certain authenticated flows.

The breadth here is notable: covering everything from recommended feed posts to TikTok Shop inventory makes TokApi useful for a wider range of projects than a typical video-only scraper.

Pricing breakdown

The API follows a freemium model with four tiers:

The free BASIC tier gives you 100 requests per month at 10 requests per minute. That is enough to test integration and explore responses, but it will be exhausted very quickly in any real-world scenario. It is best treated as an evaluation tier rather than something you would build a feature on top of.

At $12.99/month, PRO delivers 1.5 million requests — a substantial jump. At a sustained rate of 180 requests per minute, those requests would technically run out in about 139 hours of continuous operation, so for most moderate-use applications (batch jobs, scheduled crawls, on-demand lookups) the PRO plan is sufficient.

The ULTRA tier is marked as recommended by the provider and makes sense for data-intensive pipelines: 5 million requests per month at 420 requests per minute. MEGA at $49.99 is the ceiling in the standard catalogue, offering 13 million monthly requests, but the provider notes that bigger plans and additional functionality are available on request via Telegram.

Performance characteristics

The API reports a 98% average success rate across all requests in the marketplace, which is solid for a scraping-based service where upstream TikTok changes can break endpoints intermittently. Average response latency sits at 1,571 ms. That figure reflects the overhead of the service acting as an intermediary — it is not fast enough for user-facing synchronous requests, but it is fine for background data collection, scheduled jobs, and batch enrichment.

Practical use cases

• Creator analytics tools: Pull a creator's profile, video feed, and per-video comment data to build engagement metrics over time.
• Hashtag and trend monitoring: Periodically query hashtag IDs to track which videos are rising within a given topic area.
• Music and effect attribution: When given a video, resolve its music track and effects to understand content production patterns at scale.
• E-commerce research: Use the TikTok Shop endpoints to monitor flash sales and product recommendations without maintaining your own scraper.
• Live stream intelligence: Track which live streams are trending using the live ranking and search endpoints.

Things to verify before integrating

Rate limits and request budgets: At 10 requests per minute on the free tier, a pipeline that fetches user + posts + comments per creator will exhaust its monthly quota in a handful of profiles. Plan your data model around the PRO or ULTRA limits.

Latency budget: At ~1.6 seconds average, this API is not suitable for anything in a synchronous request path. Design your system to call TokApi asynchronously and cache results.

Unofficial status: TikTok can change its internal API at any time. The provider absorbs most of that maintenance burden, but there may be intervals where certain endpoints degrade. The 98% success rate accounts for this to some degree, but factor in retry logic.

Data completeness: The shown endpoints include duplicates in the listing (likely versioning artifacts), and some entries are marked as deprecated and removed. The full 82-endpoint set is documented at docs.tokapi.online/api/.

Getting started

Authentication uses two headers: X-RapidAPI-Key (your personal API key from the RapidAPI dashboard) and X-RapidAPI-Host set to tokapi-mobile-version.p.rapidapi.com. A minimal cURL call to the recommended feed looks like:

curl -X GET "https://tokapi-mobile-version.p.rapidapi.com/v1/feed/recommended?pull_type=0&region=US" \
    -H "X-RapidAPI-Host: tokapi-mobile-version.p.rapidapi.com" \
    -H "X-RapidAPI-Key: YOUR_KEY"

A Python SDK is available on GitHub at github.com/mtokapi/tokapi-client, with example scripts in the examples/ directory that cover common workflows. For questions or custom plan requests, the provider can be reached directly on Telegram.