Developers

Overview

Build against C21 Live Control — the REST API at /c21apiv2 and the MCP server, both behind one bearer token.

C21 Live Control exposes every operation in its UI programmatically. The same bearer token authenticates two surfaces: the REST API for deterministic scripting and integration, and the MCP server for AI agents and automation.

REST API

The REST API at /c21apiv2 exposes every resource visible in the operator UI: Channels, Encodings, Destinations, Live streams, Schedules, Recordings, Devices, Assets, Users, DRM providers, C21 Live Cloud accounts and the system surface. Use it to script provisioning, integrate with playout systems or build internal dashboards.

API Overview

Base URL, resources, content types, verbs, idempotency.

Authentication

API tokens, lifecycle, storage advice.

Pagination and errors

Pagination envelope, error catalogue, retry guidance.

MCP server

The Model Context Protocol server exposes a curated subset of the API operations as a toolset that any MCP-compatible AI agent or automation can call. The toolset visible to a connected client is bounded by a server-side profile.

MCP server

Transports, authentication, profiles.

Tools

Tool catalogue grouped by resource.

Examples

Configuration snippets and worked agent flows.

External integrations

Connecting Live Control to other Cires21 products — MediaCopilot, C21 Live Cloud and DRM providers — is configured in the UI, not coded against here. Those are documented under Settings → Integrations.

FAQ

Licenses

The product licenses that gate C21 Live Control and C21 Live Encoder, how they are installed, where they are administered, and what happens when one is missing or expires.

Overview

Programmatic access to C21 Live Control over its REST API.