MediaKind platform | MediaKind Docs

MediaKind builds video infrastructure for broadcasters, pay-TV operators, and streaming services. Following the June 2026 merger with Harmonic’s video business, the platform spans three product families, all documented here.

mk.io

Cloud video. Register storage, run transcode jobs, publish assets, and operate live channels and events.

Beam

Channel origination on MediaKind appliances, plus the device fleet and the networks and sites they run on.

Harmonic VOS

The VOS video processing platform — asset acquisition, playout, packaging, and scrambling.

How the APIs relate

The cloud APIs — Media, Live, Management, and Templates — share a base URL and a single bearer token, and are routinely combined in one automation flow. Beam’s APIs manage physical devices and the channels running on them. VOS is deployed per cluster and addressed at its own host.

Product	APIs	Deployment
mk.io	Media, Live, Management, Templates	Cloud, `https://app.mk.io`
Beam	Channels, Fleets, Infrastructure	Cloud control plane, on-prem devices
Harmonic	VOS	On-premises, per cluster

New here? Start with Which API to use to find the right surface for the resource you want to manage, then Authentication to get a token.

SDKs

One client per language covers every API above, with each one namespaced so the products stay distinct:

import { MediaKind } from "@mediakind/sdk";
const client = new MediaKind({ apiToken: process.env.MEDIAKIND_API_TOKEN });
const assets = await client.media.assets.list();
const channels = await client.channels.channels.list();

See TypeScript and Python for installation and the full namespace map.