Creator profiles
Public creator and account inputs for repeatable screening, capped per call and cache-first on repeat lookups.
TikTok data product
Organize creator, post, trend, and commerce signals into bounded developer contracts. Scope is explicit: research and diligence workflows, not a CPM or ad-revenue guarantee, and no upstream is named in any response.
Designed product surface
These capabilities describe the intended product contract. They do not override the status shown above.
Public creator and account inputs for repeatable screening, capped per call and cache-first on repeat lookups.
Video and interaction signals with explicit record boundaries — a stated max post count per request, not a full-catalog dump.
Research workflows that separate observed counts from forecasted trend direction; forecasts are labeled and never presented as fact.
Shop and product signals only where the specific route's contract supports them, paired with deterministic content-strategy and brand-safety scores computed from collected fields.
The API Aha difference
API management is not a catalog of optimistic endpoint names. The response contract, cache behavior, usage math, and buyer path are part of the product.
Canonical product status
This page describes the governed product surface. Access stays closed until the linked product families retain current authenticated cold and warm semantic, cache, and billing receipts.
The current repository does not retain a complete, current authenticated-subscriber cold/warm receipt for every buyer-visible operation. API Aha does not present this family as available yet.
Need this workflow?
We will not substitute a sales promise for a missing product receipt.