Skip to main content
CreatorAudit tracks public creator analytics on two platforms. This page sets expectations: which platforms and objects you can work with, which metrics the API returns, and what is intentionally out of scope.

Platforms

CreatorAudit covers Instagram and TikTok, and only these two. Every account, video, and creator carries a platform field of instagram or tiktok, and most list endpoints accept platform=instagram|tiktok as a filter.
CreatorAudit reads public engagement data only. It never accesses private accounts, direct messages, or any non-public signal.

Objects

The API models a small set of objects. They map one-to-one to the dashboard, so the same concepts appear in each — see Key concepts for the full model.

Account

A tracked Instagram or TikTok profile. CreatorAudit refreshes its profile metrics and discovers the videos in its feed.

Account video

A post discovered automatically from a tracked account’s feed. You don’t add these — they appear as the account is refreshed.

Individual video

A post you add yourself by URL, shortcode, or ID — even if you don’t track the posting account.

Creator

A grouping of one or more accounts that you define, so you can analyze a person or brand across platforms.
An organization is the workspace that owns all of the above, and your API key is scoped to a single organization. Accounts surface account videos; you group accounts into creators; and you can track individual videos independently.

Metrics

CreatorAudit exposes the public engagement metrics below. Accounts, videos, and creators carry the subset that applies to them, and analytics responses report them over a window.
MetricApplies toMeaning
FollowersAccountsAudience size of the profile.
ViewsVideosTimes a video was seen.
PlaysVideosTimes a video was played.
LikesVideosLike reactions on a video.
CommentsVideosComments on a video.
SharesVideosTimes a video was shared.
SavesVideos, accountssaved_countInstagram only; null for TikTok.
Engagement rateVideos, accounts(likes + comments + shares) / views, as a percentage.
Creator metrics roll up from the creator’s linked accounts.
Saves are returned as the saved_count field on account and video responses, but only for Instagram — it’s null for TikTok, which doesn’t expose saves.

Verified profiles

Accounts carry an is_verified boolean reflecting the platform’s verification badge. Use it to distinguish verified profiles when you filter or display results.

Windows and time series

You read metrics over a window7d, 30d, or 90d, or a custom date range — at the account, video, creator, and organization scopes. Each scope offers a single windowed snapshot and a daily time series you can chart, and period-over-period comparisons against the previous window.
Metrics are not real-time. A newly tracked account or video has last_scrape_time: null until its first refresh, and its time series fills in over the following days. Individual videos expose scrape_interval_hours to control how often they re-fetch. See Data freshness.

What’s not available

CreatorAudit does not push events. To learn when data changes, re-fetch the resource on a sensible interval and watch last_scrape_time. See Production best practices for polling guidance.
Only public engagement metrics are collected. Private accounts, direct messages, and audience demographics are out of scope.
Instagram and TikTok are the only supported platforms. Other networks aren’t covered.

Limits

A few practical limits shape how you read data:
  • Pagination. List endpoints accept limit from 1 to 200.
  • Search and leaderboards. GET /search and GET /creators/top cap limit at 25.
  • Batch metrics. Fetch windowed metrics for many IDs in one call via POST /accounts/metrics, POST /videos/metrics, and POST /account-videos/metrics (up to 200 IDs each).
CreatorAudit doesn’t publish numeric rate limits — read the X-RateLimit-* headers at runtime. See Rate limits and Pagination.

Next steps

Key concepts

How accounts, creators, and videos relate.

Data freshness

How often data refreshes and when it’s ready.

Production best practices

Ship a reliable integration end to end.

API introduction

Envelopes, conventions, and the endpoint reference.