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 PublishToken API

Create and manage publish (broadcaster) tokens.

Dolby.io PublishToken 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 PublishToken. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 3 JSON Schemas.

This API exposes 6 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2026.05.

Requests are made against a single base URL, https://api.millicast.com/api.

6 operations 4 paths 3 schemas 1 DELETE3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026.05
Server
https://api.millicast.com/api
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Dolby.io PublishToken API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API Secret) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

PublishToken 6

Create and manage publish (broadcaster) tokens.

POST
/publish_token
Create Publish Token
createPublishToken body → 200
GET
/publish_token/list
List Publish Tokens
listPublishTokens 2 params → 200
GET
/publish_token/{tokenID}
Get Publish Token
getPublishToken 1 param → 200
PATCH
/publish_token/{tokenID}
Update Publish Token
updatePublishToken 1 param body → 200
DELETE
/publish_token/{tokenID}
Delete Publish Token
deletePublishToken 1 param → 204
GET
/publish_token/account/tokens
List Active Publish Token IDs
listActivePublishTokenIds → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are PublishToken (12 properties), PublishTokenCreate (7 properties), PublishTokenUpdate (5 properties). Each schema is shown below with its type and property counts.

PublishTokenUpdate
object
5 properties
PublishToken
object
12 properties
PublishTokenCreate
object
7 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dolby-io-publishtoken-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 Channels API
Dolby.io Cluster API
Dolby.io Custom Endpoint Providers API
Dolby.io Custom Endpoints API
Dolby.io Distributions API
Dolby.io Engines API
Where this information came from

This is an independent, third-party profile of Dolby.io PublishToken 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.