getIntegrationFleetHealth
GET
/api/v1/integration/activity/fleet
const url = 'https://example.com/api/v1/integration/activity/fleet';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/integration/activity/fleetRead fleet health for integrations. An integration token authenticates this call with the activity read scope.
Responses
Section titled “ Responses ”Fleet health
Media typeapplication/json
object
data
required
Token-authenticated fleet summary for monitoring systems. Screen buckets mirror the Studio status thresholds, except there is deliberately no online count: live presence lives in the process-local socket hub, which a database read cannot see.
object
generatedAt
required
string format: date-time
screens
required
object
total
required
integer
recent
required
integer
stale
required
integer
offline
required
integer
disabled
required
integer
incidents
required
object
open
required
integer
acknowledged
required
integer
bySeverity
required
object
key
additional properties
integer
content
required
object
staleDataSources
required
integer
emptyPlaylists
required
integer
Examplegenerated
{ "data": { "generatedAt": "2026-04-15T12:00:00Z", "screens": { "total": 1, "recent": 1, "stale": 1, "offline": 1, "disabled": 1 }, "incidents": { "open": 1, "acknowledged": 1, "bySeverity": { "additionalProperty": 1 } }, "content": { "staleDataSources": 1, "emptyPlaylists": 1 } }}Integration authentication required
Insufficient scope