What's Happening?
Zoom Developers have released a preview of their November update for the Real-time Messaging Service (RTMS), introducing significant enhancements to participant and audio data handling. A key new feature is the `MEDIA_DATA_USER_INFO` event, which will
automatically identify participants whose audio, video, screen share, transcript, or chat data has been observed by the service. This event will include `user_id`, `user_name`, and `participant_uuid`, and will be sent automatically in the `EVENT_UPDATE` message without requiring a subscription, specifically for Zoom Meetings. Additionally, the `MEDIA_DATA_AUDIO` event will now include a `content.source` field, allowing developers to distinguish between microphone audio (value `1`) and shared-content audio (value `2`), which is crucial for separating screen-share audio from microphone input. These updates are part of a broader RTMS V2 protocol release that also includes application-layer media encryption, Zoom Phone support, transcript rewind capabilities, and multiple individual video streams.
Why It's Important?
These new features are important for developers building applications that integrate with Zoom, as they provide more granular control and information about meeting participants and audio sources. The `MEDIA_DATA_USER_INFO` event simplifies the process of identifying active participants and their data streams, which can enhance the development of analytics tools, compliance monitoring systems, and interactive meeting applications. The ability to differentiate between microphone and shared-content audio in `MEDIA_DATA_AUDIO` is particularly valuable for applications requiring precise audio processing, such as transcription services, noise cancellation, or content moderation, ensuring that the correct audio source is being analyzed. These improvements aim to provide a richer, more detailed data stream from Zoom meetings, enabling more sophisticated and tailored user experiences and integrations for businesses and developers.
What's Next?
The changes outlined in the RTMS November release preview are not yet live but are intended to allow developers to plan their integrations ahead of the official release. Developers should review the new V2 protocol, including the protobuf wire format and SRT transport for data connections, to prepare their applications for compatibility and to leverage the new functionalities. Starting November 15, 2026, RTMS will also require TLS 1.2 or TLS 1.3 for all connections, meaning developers must ensure their client connection requests use one of these supported versions to avoid rejection. The new features, such as application-layer media payload encryption, will be available by request and require approval from the Zoom team. Developers will need to adapt their systems to utilize the new event codes and data structures for optimal performance and security.
Beyond the Headlines
The continuous evolution of Zoom's developer platform, particularly with enhanced participant and audio data, reflects a broader trend in communication technology towards more intelligent and context-aware interactions. By providing detailed metadata about who is speaking and what content is being shared, Zoom is enabling a new generation of AI-powered tools that can analyze meeting dynamics, automate summaries, and improve accessibility. This level of data granularity also raises important considerations regarding privacy and data governance, as more information about user activity becomes programmatically accessible. Developers and organizations will need to implement robust data handling policies to ensure responsible use of these enhanced capabilities, balancing innovation with user trust and regulatory compliance. The move towards more secure protocols like TLS 1.2/1.3 also underscores the industry's commitment to safeguarding sensitive communication data.
