How To Enable RTMS for my account

Realtime Media Streams
1

Hi,

I am currently a Zoom Workplace Basic user and am working on a POC of integrating RTMS (Real-time Media Streaming) into my application so that I can capture the live meeting transcripts and provide live AI support to our customer. However, I’ve encountered a few roadblocks and would appreciate some guidance.

1.Events Configuration Issues** I am currently configuring server to server oauth app in the Marketplace Build flow. I am unable to find specific events like meeting:rtms_started, which I understand are necessary for RTMS. Is there a specific app type or account requirement to enable these events?

2. Webhook and WebSocket Connection Issue I have successfully received the meeting.started webhook event. However, I am not receiving the specific RTMS streaming start event, which is preventing me from establishing a WebSocket connection.

Current Setup:

  • Environment: Development

  • Status: Successfully receiving standard meeting webhooks.

  • Problem: No RTMS-related events triggered, so the WS connection cannot be initiated.

Could you please advise if there are additional settings I need to enable in the Zoom web portal or if I am missing a specific configuration in the App Marketplace?

Thank you in advance for your help!

RTMS Available Events:

rtms:read:rtms_interrupted:admin The RTMS Interrupted event is triggered when an ongoing meeting stream gets disrupted due to a broken signaling socket connection.
rtms:read:zcc_voice_rtms_started:admin ZCC Voice RTMS started event granular scope
rtms:read:zcc_voice_rtms_stopped:admin ZCC Voice RTMS stopped event granular scope
rtms:read:rtms_concurrency_limited:admin The RTMS Concurrency Limited event is triggered when the concurrency limit of a specific RTMS app is reached.
rtms:read:zcc_voice_rtms_interrupted:admin ZCC Voice RTMS interrupted event granular scope
rtms:read:rtms_concurrency_near_limit:admin The RTMS Concurrency Near Limit event is triggered when the app is nearing the predetermined concurrency limit.
3

What’s likely missing here is RTMS enablement. Zoom’s current RTMS setup docs still say you need that enabled for your account and app, even though RTMS is generally available. Until that’s in place, it’s expected that the RTMS scopes and events may not appear in Marketplace build flow, so a Workplace Basic account plus a fresh Server-to-Server OAuth app is not enough on its own.

Also, meeting.started is not the event that boots the stream. Zoom documents that meeting.rtms_started carries the initial session details like meeting_uuid and rtms_stream_id that your backend needs before it can connect. I also don’t see docs that show Server-to-Server OAuth by itself as the RTMS trigger path. The documented trigger path is a Zoom App calling startRTMS().

Two checks that should unblock this fast. First, after RTMS enablement is applied, verify your app can add the RTMS scopes and subscribe to meeting.rtms_started and meeting.rtms_stopped in Marketplace. Second, test from a meeting where the RTMS-capable app is actually used to start RTMS, then wait for meeting.rtms_started before opening the WebSocket.

We’re a Zoom RTMS Preferred Partner, so if you want a faster path or a second sanity check on setup, Recall.ai can help.

4

Hi Amanda,

Thanks for the quick response!

I’ve already submitted a request to enable RTMS for my account, but it hasn’t been completed yet. As a result, I’m unable to subscribe to the meeting.rtms_started and meeting.rtms_stopped events. Could you please advise if there’s a way to expedite this process?

5

@Amit11 we’re an RTMS Preferred Partner, so you can use RTMS through Recall.ai.

If you create an account with Recall.ai, email me (amanda@recall.ai) with this thread, and I’ll enable RTMS on your Recall.ai account.