Streaming API Overview

The Streaming APIs enable customer's application to stream the conference to a large number of viewers. Real-time Streaming (RTS) and Real-Time Messaging Protocol (RTMP) are supported for live conferences. RTMP is used for streaming through a third-party service such as Youtube and Facebook.

RTS allows a customer to stream conferences to up to 100k viewers over low latency WebRTC using Millicast streaming services. RTS requires the Millicast stream name and the publishing token parameters that are available in the Millicast dashboard. Using these parameters, customers can call the RTS REST APIs to start or stop streaming to an RTMP endpoint.

The concept of Streaming is similar to Recording. The Communications API Mixer Service, using either default or customized layout, can stream to a destination based on the method chosen by the application. The customizable mixer layout app, has the flexibility to implement use case specific layouts. In other words, a customer can have different layouts for recording. It is not possible to stream a recorded conference.

You can specify a layoutName using the Streaming APIs. The layoutName is useful in identifying the layout referenced in other API calls, error messages, and webhooks. The Streaming APIs also support the ability to set a custom layoutUrl, that overrides the layout URL specified in the dashboard. Note: The Dolby.io Communications APIs do not currently support multiple same type streaming tasks running at the same time with different layouts.

For more information regarding the streaming format, refer to this page.