The short answer
TikAPI exposes a public/account-key split, while TikHub separates app, web, Shop, Ads and account-authorized Creator series. For public content, compare only public routes. If account insights are required, review the authorization and credential handling independently rather than treating the two providers' account mechanisms as interchangeable OAuth flows.
| Provider | A good reason to choose it | Important caveat |
|---|---|---|
| TikAPI | A TikTok-specific integration that needs to distinguish public reads from operations requiring a user's explicit account authorization. | TikAPI is not TikTok's official developer API. Its account-key authorization is a different integration from TikTok Display API OAuth. Public profile access does not grant permission to operate another person's account. |
| TikHub | A TikTok-heavy integration that needs distinct video, Shop and ad-research routes rather than only a basic public profile lookup. | App, Web, Shop and Creator APIs are not interchangeable. The Creator API requires the account owner's authorized login cookie; public video access does not unlock private creator analytics. Keep those credentials outside a general public-data adapter. |
Side-by-side differences
| Requirement | TikAPI | TikHub |
|---|---|---|
| Integration model | TikTok-specific public and account-authorized interfaces | Separate App V3, Web, Shop, Creator and Ads API series |
| TikTok coverage | Public profiles and content; account functions require separate authorization | Public videos, profiles, comments, search, live and dedicated Shop routes |
| Response lifecycle | Public check returns directly; sandbox is a separate host | Direct REST reads; account-specific operations have extra requirements |
| Pagination and identifiers | Username-based profile check; preserve userInfo identifiers as strings | aweme_id and route-specific cursors; preserve ID strings |
| Billing unit | Plan allowances and endpoint entitlements must be confirmed | Per-request pricing and volume tiers; confirm endpoint cost |
| Operational boundary | Unofficial service; account keys are not official TikTok OAuth tokens | Creator analytics require authorized account access, not public-read credentials alone |
Pricing: make the units comparable
| Provider | Billing model | What to check |
|---|---|---|
| TikAPI | Plan-dependent API access | Confirm current request allowances, public/account endpoint entitlements, overages and sandbox behavior in the chosen TikAPI plan. The endpoint reference is not enough to establish a universal per-record price; no numeric price is assumed here. |
| TikHub | Pay-as-you-go request pricing | The reviewed TikTok product page advertises a $0.001/request starting price, volume discounts and $0.05 signup credit without a card. Confirm the exact series and endpoint charge; do not apply a volume minimum to every workload. |
For a workload of 1,000 public profiles and 10,000 recent videos, count profile calls, all video pages, duplicates, empty pages and optional comments separately. A prepaid request credit, an endpoint-weighted daily unit and a delivered-record charge are different units. Keep cached reads separate from fresh collection.
For a buying decision, calculate total spend divided by accepted outputs at your expected volume. Keep free evaluation access, paid production access, annual commitments and overages separate. We have not measured a cost or speed winner for this pair.
What changes in the integration?
| TikAPI | TikHub | |
|---|---|---|
| Method and URL | GET https://api.tikapi.io/public/check | GET https://api.tikhub.io/api/v1/tiktok/app/v3/fetch_one_video |
| Authentication | X-API-KEY header for public reads; authorized-account operations additionally use an account key | Authorization: Bearer YOUR_API_KEY; some authorized creator operations need additional account credentials |
| Inputs | username query parameter; optional country context | aweme_id query parameter containing a TikTok video ID |
| Output | Profile information and statistics under userInfo, alongside status fields; not an exhaustive post or follower export. | Video data with author, statistics and music fields under data; unavailable fields and platform error codes need separate handling. |
TikAPI: migration check
Separate the application API key from any user account key. Map userInfo.user and userInfo.stats rather than assuming a shared top-level profile schema. Moving to official Display API also changes identity, scopes and authorization, not just the base URL.
TikHub: migration check
Pin the API series, not only the hostname. Convert video IDs to aweme_id inputs without numeric coercion, keep route-specific cursors opaque and do not fall back from a public read to an account-authenticated endpoint automatically.
How to test them fairly
- Choose a small fixture of public profiles, video URLs and keywords that you have a legitimate reason to process. Do not request private accounts or use account cookies without the owner's authorization.
- Collect the same inputs within a narrow time window. Record region, language, cache settings and collection time; changing engagement counts do not establish which response was more accurate.
- Keep video IDs and creator IDs as strings. Test handle changes, duplicates across pages, empty results, removed videos and missing comments. A successful HTTP response is not evidence of complete coverage.
- Measure direct-request latency separately from end-to-end job completion. For an asynchronous provider, include queueing, status checks and dataset retrieval rather than timing only job creation.
- Record accepted unique rows, pages, billed credits or units, optional enrichments and retries. Calculate cost per accepted profile or video; do not equate one HTTP call with one returned record.
- Confirm the intended use, retention and redistribution rights before production. Public availability and an API subscription do not by themselves grant permission to republish videos, music or personal data.
Record the plan, request settings, time window and acceptance rules with every run. That makes a later result interpretable when a vendor changes a model, source set or pricing tier.
Prefer a common request format?
POST /api/v1/tiktok/searchReview the request contract and tell us the coverage you need. Access requires enablement; this endpoint does not execute or bill requests yet.
View endpoint and request accessSources and review dates
Documentation reviewed October 28, 2026. These are integration and plan comparisons, not measured speed or accuracy rankings. Availability, licensing and prices should be confirmed for the chosen plan.
- TikAPI public and account API reference
- TikAPI product and plans
- TikHub TikTok API series, endpoints and pricing
- TikHub developer documentation
Corrections: email faizank@docsalot.dev with an official source.