Skip to Content
API ReferenceAnalyticsOverview

Analytics API

The Analytics API lets you read playback metrics for your workspace. All endpoints are read-only GET requests under /api/analytics/*.

Your API key must have the analytics.read permission. Video read alone is not enough. See Authentication.

Endpoints

EndpointPath
PlaysGET /api/analytics/plays
SourcesGET /api/analytics/sources
ContentGET /api/analytics/content
BreakdownGET /api/analytics/breakdown
CompletionGET /api/analytics/completion
WatchingGET /api/analytics/watching
EngagementGET /api/analytics/engagement
LiveGET /api/analytics/live

Authentication

Pass your API key as a Bearer token:

curl -H "Authorization: Bearer YOUR_API_KEY" \ "https://app.ignitevideo.cloud/api/analytics/plays?interval=day"

The workspace is taken from the API key. Do not send a workspaceId query parameter.

Category scope

If your API key is limited to specific categories:

  • Workspace-wide analytics calls (no video contentId) still return full-workspace aggregates.
  • Per-video calls that pass a VOD contentId only succeed when that video is inside the key’s category scope.
  • Live content (contentType=live) is not filtered by category scope.

Common query parameters

Many endpoints share these parameters:

ParameterTypeDescription
contentTypestringvod (default) or live
contentIdstringVideo id or live event id
fromstringISO 8601 start time. Defaults to about 30 days ago.
tostringISO 8601 end time. Defaults to now.
minimumWatchSecondsnumberMinimum watch time for a view to count. Default is 3.
intervalstringFor plays: hour or day (default day)
limitnumberMax rows for ranked lists. Default is 100.

Ranges wider than about one year are clamped to the most recent year.

Errors

StatusBodyMeaning
400{ "error": "..." }Invalid query parameters
403Missing analytics.read, disabled key, or out-of-scope VOD contentId
500{ "error": "analytics_not_configured" }Analytics is not configured on the server
502{ "error": "analytics_upstream_error" }Upstream analytics error
504{ "error": "analytics_timeout" }Upstream analytics timeout

Responses include Cache-Control: private, no-store. Do not cache analytics responses in the browser across workspace switches.