The short answer
ScrapeCreators offers direct social reads with endpoint-specific credits and optional cached results. TikHub divides TikTok into several specialized API series, including Shop and Ads. Start with the exact required surface: a public profile lookup does not justify integrating authorized creator analytics, and a Shop project needs its own endpoint review.
| Provider | A good reason to choose it | Important caveat |
|---|---|---|
| ScrapeCreators | An application that needs a public profile or video page inside an ordinary request/response adapter rather than managing a collection job. | The documented cache option changes freshness as well as cost. Profile, video-list and transcript endpoints have separate versions and response shapes; do not assume one version prefix covers every route. |
| 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 | ScrapeCreators | TikHub |
|---|---|---|
| Integration model | Versioned REST endpoints with an API-key header | Separate App V3, Web, Shop, Creator and Ads API series |
| TikTok coverage | Public profiles, videos, search, comments, transcripts and Shop routes | Public videos, profiles, comments, search, live and dedicated Shop routes |
| Response lifecycle | Direct JSON responses; explicit cache-age option | Direct REST reads; account-specific operations have extra requirements |
| Pagination and identifiers | Handle/user ID inputs; list cursors depend on the endpoint | aweme_id and route-specific cursors; preserve ID strings |
| Billing unit | Endpoint credits; qualifying cached reads may cost zero | Per-request pricing and volume tiers; confirm endpoint cost |
| Operational boundary | Cache freshness and differing endpoint versions need explicit handling | Creator analytics require authorized account access, not public-read credentials alone |
Pricing: make the units comparable
| Provider | Billing model | What to check |
|---|---|---|
| ScrapeCreators | Prepaid credits; endpoint-specific consumption | The public profile endpoint lists one credit per request. A qualifying cache_max_age hit is documented at zero credits; a cache miss uses the normal endpoint charge. Purchased credits are advertised as non-expiring. Check each selected endpoint rather than assuming every call costs one credit. |
| 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?
| ScrapeCreators | TikHub | |
|---|---|---|
| Method and URL | GET https://api.scrapecreators.com/v1/tiktok/profile | GET https://api.tikhub.io/api/v1/tiktok/app/v3/fetch_one_video |
| Authentication | x-api-key: YOUR_API_KEY | Authorization: Bearer YOUR_API_KEY; some authorized creator operations need additional account credentials |
| Inputs | handle or user_id query parameter; optional cache_max_age | aweme_id query parameter containing a TikTok video ID |
| Output | Public user and stats fields plus success, credits_charged and credits_remaining. | Video data with author, statistics and music fields under data; unavailable fields and platform error codes need separate handling. |
ScrapeCreators: migration check
Map handle/user_id explicitly and retain credits_charged for reconciliation. Decide whether cached observations are acceptable before enabling cache_max_age; a cheaper cached count is not a fresh measurement.
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.
- ScrapeCreators TikTok profile reference
- ScrapeCreators endpoint directory
- ScrapeCreators credit and cache model
- TikHub TikTok API series, endpoints and pricing
- TikHub developer documentation
Corrections: email faizank@docsalot.dev with an official source.