Changelog: RTMS - Apps can now start RTMS for a host before they join a meeting

Released: 2026-01-18 Updated: 2026-01-22T16:08:48

Visit Changelog

Summary: The Update participant Real-Time Media Streams (RTMS) app status API has been updated.
The Update participant Real-Time Media Streams (RTMS) app status API has been updated to remove the requirement that a host be in a meeting for their app to be started, paused, resumed, or stopped.

Apps can now use the REST API to start RTMS in meetings that allow participants to join before the host.

A number of meeting use cases, like interviews or telehealth visits, where the original owner of the meeting may not join are now available using the REST API. This also allows account-level REST API control over internal applications.

Previously, these apps relied on an app to auto-start for RTMS to begin. We spoke to many apps developers looking to control the business logic for a stream through the REST API. This opens up more permissive access for flexible workflows.

With this update, apps can now successfully start RTMS with a meeting host’s OAuth access token, even if they have not yet joined. Alternative hosts still require in-meeting presence to start RTMS.