Build with the Media API

The Media API is the operational API for media processing and delivery in MK.IO. Use it when you need to register storage, create assets, run transforms and jobs, manage live events, publish content with streaming locators, or protect playback with streaming and content key policies.

API overview

How the core resources connect

The Media API becomes much easier to use once you understand the sequence:

1. A storage instance tells MK.IO how to reach cloud storage.
2. An asset points to content in that storage.
3. A transform defines processing instructions.
4. A job applies the transform to the asset and creates output assets.
5. A streaming locator publishes an asset by linking it to a streaming policy.
6. A streaming endpoint provides the delivery domain for the playback paths returned by listPaths.
7. A content key policy becomes part of the chain when you need DRM or token-based key delivery.

That resource model supports both VOD and live workflows. The difference is whether the asset is created from existing stored content or continuously written by a live output.

Common workflow patterns

VOD workflow

1. Register storage
2. Create a source asset
3. Run a transform job
4. Publish with a streaming locator

Live workflow

1. Register storage
2. Create and start a live event
3. Create a live output to archive the stream
4. Publish with a streaming locator

Protected playback

1. Publish with a DRM-capable streaming policy
2. Create a content key policy
3. Create a streaming locator referencing both

Guides

• Storage: Register Azure, AWS, or Google storage and manage the credentials MK.IO uses to access it.
• Assets: Create assets, inspect tracks, request file access information, organize content with labels, and apply filters.
• Download asset files: Retrieve one file from an asset by requesting access information, then using the returned access URL and JWT.
• Playback filters: Create asset or account filters for time ranges, track selection, and startup quality, then apply them through locators.
• Transforms and jobs: Define reusable processing profiles and run them against assets.
• Live streaming: Create live events, connect encoders, archive with live outputs, and publish live playback.
• Streaming and publishing: Create streaming endpoints, locators, and policies, then retrieve playback URLs.
• Content protection: Add DRM and key-delivery configuration to published assets.

Workflow guide

• Automate a VOD pipeline: Follow an end-to-end flow from source asset through transform job to published playback.