Casing Convention
Two conventions coexist:
- Discovery API: camelCase (e.g.,
engagementRate, avgLikes)
- Raw API: snake_case (mirrors platform-native field names)
The Discovery API is the primary product offered to customers.
Identity & Profile (Discovery API)
| Field Path | Type | Description |
|---|
userId | string | Creator identifier |
userId.
Follower Counts
| Field Path | Type | Description |
|---|
followers | integer | Total follower count |
followers without _count suffix.
Engagement Metrics
| Field Path | Type | Description |
|---|
engagementRate | float | Engagement rate |
avgLikes | integer | Average likes per post |
Audience — Location
| Field Path | Type | Description |
|---|
audienceGeo | object | Audience geography distribution |
Audience — Gender
| Field Path | Type | Description |
|---|
genders | object | Audience gender distribution |
Audience — Age
| Field Path | Type | Description |
|---|
ages | object | Audience age distribution |
Audience Authenticity
| Field Path | Type | Description |
|---|
followerTypes | object | Breakdown of follower types (real, suspicious, etc.) |
audienceCredibility | float | Overall audience quality/credibility score |
Gaps in Public Documentation
The following areas are referenced in marketing materials but field-level schemas are behind authentication:
- Growth/trending metrics
- Content detail fields
- Sponsorship detection fields
- Contact information fields
- Ranking/scoring fields
Last modified on March 25, 2026
