Profiles and identity
Canonical public profile inputs with bounded, product-scoped collection — one profile fetch, one accounted record.
Instagram data product
Structure public profile, content, and engagement inputs for diligence and reporting. API Aha computes scores deterministically from the fields it actually collects; it does not manufacture demographic, fraud, or revenue facts that no verified field supports, and does not disclose which upstream sourced any given field.
Designed product surface
These capabilities describe the intended product contract. They do not override the status shown above.
Canonical public profile inputs with bounded, product-scoped collection — one profile fetch, one accounted record.
Content research surfaces with explicit per-call limits and a stated freshness window, not an unlimited archive claim.
Comparable response shapes across accounts of the same type so recurring client reports diff cleanly month to month.
Engagement-quality and growth-forecast scores are formula-driven and labeled as estimates with retained methodology — never presented as measured audience demographics.
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.