Dolby Monitoring API

The Monitoring API from Dolby — 9 operation(s) for monitoring.

Operations 9

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /api/monitoring/streams List live and recent streams in detail · List Streams #
Ask an LLM
“Which streams are live right now or ended in the last hour?”
“Can I list only multisource or restreaming streams that are active?”
Tell an agent
List detailed info on all active and recently ended streams.
Show detailed stream monitoring for streams matching {searchSubstring}.
GET /api/monitoring/streams/{streamName} Get full monitoring details of a stream · Stream Details #
Ask an LLM
“What are the full feed details of a stream I'm monitoring?”
“Does getting stream details need the LiveMonitoring feature?”
Tell an agent
Show full stream details for {streamName}.
Get the feed-level monitoring details of stream {streamName}.
GET /api/monitoring/summary List a lightweight summary of streams · List Stream Summary #
Ask an LLM
“Can I get a quick summary list of active and recently ended streams?”
“Is there a lighter stream list I can filter by cluster?”
Tell an agent
List a summary of active and recently ended streams.
Show stream summaries in cluster {cluster}.
GET /api/monitoring/summary/{streamName} Get a lightweight summary of one stream · Stream Summary #
Ask an LLM
“Can I get a stream's summary without all the feed details?”
“What is the quick status of one stream by name?”
Tell an agent
Show the summary of stream {streamName}.
Get a lite status for stream {streamName} without feed details.
GET /monitoring/channels/{channelId} Get health status of a channel · Get monitoring data for a channel #
Ask an LLM
“Are a channel's ingests, engines and distributions healthy right now?”
“Can I check the overall status of one channel at a glance?”
Tell an agent
Show monitoring status for channel {channelId}.
Check the health of channel {channelId}.
GET /monitoring/ingests/{ingestId} Get metrics for one ingest · Get detailed monitoring data for an ingest #
Ask an LLM
“What packet loss and round-trip time is one ingest seeing?”
“Can I get bitrate metrics for a single ingest over a time window?”
Tell an agent
Show monitoring metrics for ingest {ingestId}.
Get packet loss and bitrate for ingest {ingestId} from {start} to {end}.
GET /monitoring/engines/{engineId} Get rendition metrics for one engine · Get detailed monitoring data for an engine #
Ask an LLM
“How are the renditions of a single engine performing?”
“Can I see one engine's rendition metrics over a time window?”
Tell an agent
Show monitoring metrics for engine {engineId}.
Get rendition metrics for engine {engineId} from {start} to {end}.
GET /monitoring/channels/{channelId}/ingests Get metrics for all ingests of a channel · Get detailed ingest monitoring data for a channel #
Ask an LLM
“How are all the ingests on a channel performing together?”
“Can I pull ingest metrics for every feed on one channel at once?”
Tell an agent
Show detailed ingest metrics for every ingest on channel {channelId}.
Get ingest monitoring for channel {channelId} from {start} to {end}.
GET /monitoring/channels/{channelId}/engines Get metrics for all engines of a channel · Get detailed engine monitoring data for a channel #
Ask an LLM
“How are all the engines on a channel performing?”
“Can I pull rendition metrics for every engine of one channel at once?”
Tell an agent
Show detailed engine metrics for every engine on channel {channelId}.
Get engine monitoring for channel {channelId} from {start} to {end}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/dolby:dolby-monitoring-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

dolby-monitoring-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Dolby Monitoring API
  version: '1.0'
  description: 'Operations tagged Monitoring across 2 of this provider''s published API definitions: dolby-millicast-api-openapi-original.json, dolby-optiview-live-openapi-original.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.millicast.com
- url: https://api.theo.live/v2
  description: V2 API
- url: https://api.theo.live
  description: Base (for /v1 endpoints)
tags:


# --- truncated at 32 KB (45 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/dolby/refs/heads/main/openapi/dolby-monitoring-api-openapi.yml