Channel profiles
Public channel identity and follower-count inputs for repeatable streamer screening.
Twitch data product
Channel, stream, clip, and game-category inputs for streamer diligence and content reporting. Scope stops at what is actually returned per call — no total-viewership or ad-revenue claim, and no upstream disclosure.
Designed product surface
These capabilities describe the intended product contract. They do not override the status shown above.
Public channel identity and follower-count inputs for repeatable streamer screening.
Live-status, clip, and video signals bounded to explicit per-call record caps, not a running historical feed.
Game-category discovery limited to the current, present-tense catalog state — not a trend-history guarantee.
Growth-forecast, audience-quality, and brand-safety scores are computed by a fixed formula with retained inputs, distinct from any unverifiable sponsorship-earnings claim.
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.