Getting Started

Release Notes

Version 1.0


We introduced a new API to enhance the analytics feature by providing watch time reports. The watch time report is a powerful tool for tracking the total time viewers spend watching your content.


We announced the addition of two new features:

  • Bring Your Own (BYO) CDN: We understand the importance of flexibility and choice regarding content delivery networks (CDNs). That's why we're introducing the BYO CDN feature. This feature allows you to choose between BlendVision CDN or your own custom CDN.
  • Chatroom: To enhance user engagement and interaction during live events or discussions, we've added a Chatroom feature. This feature provides real-time communication capabilities, allowing users to exchange messages and interact with each other seamlessly. We also provide a Word Filter feature for Chatroom to prevent inappropriate messages.


We have introduced two new APIs to enhance the billing feature by providing CSV reports. These APIs provide a more efficient way to manage and access billing information, making it easier to keep track of your usage and costs.


  • We offer a new ingestion method, WebRTC, for lower latency live streaming.
  • We've incorporated a new feature that enables users to create and control two-way meeting rooms utilizing WebRTC. This development is set to help how users conduct meetings, fostering real-time engagement and communication with significantly lower latency.


Starting from this version, we are introducing the x-kk-org-id to facilitate the management of multiple organizations. You can define the x-kk-org-id header with your organization's ID for specific APIs.

This added functionality permits you to conduct operations representing various organizations, utilizing the same authorization token but designating a distinct organization ID. Verifying that you possess the appropriate permissions to act on behalf of the organization specified is essential.


Upgrade the auth mechanism from API keys to bearer authentication. Since this version, you should include the API key in the Authorization header as a Bearer token to authenticate the API requests.


We've released new updates to the following APIs:

These APIs are now generally available. More APIs you can find in the API reference.