How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Dolby.io Channels API

The Channels API from Dolby.io — 20 operation(s) for channels.

Dolby.io Channels API is one of 18 APIs that Dolby.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Channels. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 3 JSON Schemas.

This API exposes 27 operations across 20 paths, and defines 34 schemas. It is described by OpenAPI 3.2.0, at version v2.

Requests are made against 2 base URLs: https://api.theo.live/v2, https://api.theo.live.

27 operations 20 paths 34 schemas 1 DELETE17 GET1 PATCH8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Servers
https://api.theo.live/v2
https://api.theo.live
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Dolby.io Channels API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

Paths & Operations 27

Across 20 paths, the API surfaces 27 operations — 1 DELETE, 17 GET, 1 PATCH, 8 POST. Each is listed below with its method, path, parameters, and response codes.

Channels 27
GET
/channels
Get all channels
get-channels 7 params → 200
POST
/channels
Create a new channel
create-channel body → 200
GET
/channels/{id}
Get a channel by ID
get-channel 2 params → 200
PATCH
/channels/{id}
Update a channel by ID
update-channel 1 param body → 200
DELETE
/channels/{id}
Delete a channel by ID
delete-channel 1 param → 204
POST
/channels/{id}/start
Start a channel (will start all connected engines)
start-channel 1 param → 204
POST
/channels/{id}/stop
Stop a channel (will stop all connected engines)
stop-channel 1 param → 204
GET
/channels/{id}/ingests
Get ingests of a channel
get-channel-ingests 3 params → 200
POST
/channels/{id}/ingests
Create an ingest for a channel
create-channel-ingest 1 param body → 200
GET
/channels/{id}/engines
Get engines of a channel
get-channel-engines 3 params → 200
POST
/channels/{id}/engines
Create an engine for a channel
create-channel-engine 1 param body → 200
GET
/channels/{id}/distributions
Get distributions of a channel
get-channel-distributions 3 params → 200
POST
/channels/{id}/distributions
Create a distribution for a channel
create-channel-distribution 1 param body → 200
POST
/channels/{id}/instream-metadata/{uuid}
Send instream metadata for a channel
send-channel-instream-metadata 2 params body → 200
GET
/channels/{id}/runs
Get engine runs of a channel
get-channel-runs 6 params → 200
GET
/channels/{id}/analytics/transcoding-minutes
Get transcoding minutes analytics for a channel
get-channel-transcoding-minutes 7 params → 200
GET
/channels/{id}/analytics/viewing-minutes
Get viewing minutes analytics for a channel
get-channel-viewing-minutes 8 params → 200
GET
/channels/{id}/analytics/bytes-transferred
Get bytes transferred analytics for a channel
get-channel-bytes-transferred 7 params → 200
GET
/channels/{id}/analytics/viewing-minutes/browsers
Get viewing minutes grouped by browser for a channel
get-channel-viewing-minutes-browsers 6 params → 200
GET
/channels/{id}/analytics/viewing-minutes/countries
Get viewing minutes grouped by country for a channel
get-channel-viewing-minutes-countries 6 params → 200
GET
/channels/{id}/analytics/bytes-transferred/browsers
Get bytes transferred grouped by browser for a channel
get-channel-bytes-transferred-browsers 6 params → 200
GET
/channels/{id}/analytics/bytes-transferred/countries
Get bytes transferred grouped by country for a channel
get-channel-bytes-transferred-countries 6 params → 200
GET
/channels/{id}/analytics/insights/countries
Get country insights for a channel
get-channel-insights-countries 5 params → 200
GET
/channels/{id}/analytics/insights/browsers-os
Get browser and OS insights for a channel
get-channel-insights-browsers-os 5 params → 200
GET
/channels/{id}/analytics/insights/viewers
Get viewer count insights for a channel
get-channel-insights-viewers 5 params → 200
POST
/channels/{id}/custom-endpoints
Create a custom endpoint on a channel
create-custom-endpoint 1 param body → 200
GET
/channels/{id}/custom-endpoints
List all custom endpoints of a channel
get-channel-custom-endpoints 1 param → 200

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are Distribution (15 properties), CreateDistributionBody (12 properties), Channel (12 properties), CustomEndpoint (12 properties). Each schema is shown below with its type and property counts.

CreateCustomEndpointBody
object
7 properties 6 required
PaginatedChannelResult
object
2 properties 2 required
Channel
object
12 properties 7 required
IncludedEngines
object
Included engines preview
4 properties 4 required
PaginatedEngineRunResult
object
2 properties 2 required
CountryInsightsListResult
object
1 property 1 required
ChannelCreatedObjectResult
object
1 property 1 required
Ingest
object
8 properties 8 required
IncludedIngests
object
Included ingests preview
4 properties 4 required
SendInstreamMetadataBody
string
Binary blob of instream metadata
IncludedDistributions
object
Included distributions preview
4 properties 4 required
PaginatedEngineResult
object
2 properties 2 required
DistributionObjectResult
object
1 property 1 required
ChannelObjectResultWithIncludes
object
4 properties 1 required
CustomEndpointObjectResult
object
1 property 1 required
CustomEndpointDrmConfig
object
Optional DRM configuration
4 properties 1 required
CreateChannelBody
object
9 properties 1 required
ViewingCountryListResult
object
1 property 1 required
ViewingBrowserListResult
object
1 property 1 required
AnalyticsListResult
object
1 property 1 required
EngineRun
object
8 properties 5 required
CustomEndpointListResult
object
1 property 1 required
Distribution
object
15 properties 8 required
CustomEndpoint
object
Custom endpoint object
12 properties 11 required
PaginatedIngestResult
object
2 properties 2 required
UpdateChannelBody
object
7 properties
ViewersInsightsListResult
object
1 property 1 required
ChannelObjectResult
object
1 property 1 required
ChannelCreated
Created channel with connected resources
EngineObjectResult
object
1 property 1 required
BrowserOsInsightsListResult
object
1 property 1 required
PaginatedDistributionResult
object
2 properties 2 required
IngestObjectResult
object
1 property 1 required
CreateDistributionBody
object
12 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dolby-io-channels-api-openapi.yml Raw ↑

Other APIs Dolby.io publishes across the network.

Dolby.io Media API
Dolby.io Communications API
Dolby OptiView Ads API
Dolby OptiView Player SDK (THEOplayer)
Dolby.io ABR Ladders API
Dolby.io Analytics API
Dolby.io Cluster API
Dolby.io Custom Endpoint Providers API
Dolby.io Custom Endpoints API
Dolby.io Distributions API
Dolby.io Engines API
Dolby.io Ingests API
Where this information came from

This is an independent, third-party profile of Dolby.io Channels API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.