# How To Enable RTMS for my account

**URL:** <https://devforum.zoom.us/t/how-to-enable-rtms-for-my-account/142626>\
**Category:** Realtime Media Streams\
**Created:** [March 28, 2026, 8:33am UTC](https://devforum.zoom.us/t/how-to-enable-rtms-for-my-account/142626 "2026-03-28T08:33:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amit11](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amit11/32/50555_2.png) [@Amit11](https://devforum.zoom.us/u/Amit11)\
**Post date:** [March 28, 2026, 8:33am UTC](https://devforum.zoom.us/t/how-to-enable-rtms-for-my-account/142626/1 "2026-03-28T08:33:08Z")

</div>

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. | | |

---

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [March 30, 2026, 11:22pm UTC](https://devforum.zoom.us/t/how-to-enable-rtms-for-my-account/142626/3 "2026-03-30T23:22:16Z")

</div>

What’s likely missing here is [RTMS enablement](https://developers.zoom.us/docs/rtms/meetings/getting-started/). Zoom’s current RTMS setup docs still say you need that enabled for your account and app, even though RTMS is [generally available](https://developers.zoom.us/changelog/rtms/june-25-2025/). 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](https://developers.zoom.us/docs/rtms/event-reference/) 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()](https://developers.zoom.us/changelog/rtms/july-14-2025/).

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](https://docs.recall.ai/docs/meeting-direct-connect-for-zoom-rtms?utm_source=zoom&utm_medium=forum_answer), so if you want a faster path or a second sanity check on setup, Recall.ai can help.

---

<div class="post-metadata">

**Author:** ![Amit11](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amit11/32/50555_2.png) [@Amit11](https://devforum.zoom.us/u/Amit11)\
**Post date:** [March 31, 2026, 2:18am UTC](https://devforum.zoom.us/t/how-to-enable-rtms-for-my-account/142626/4 "2026-03-31T02:18:42Z")

</div>

> [@amanda-recallai](#):
>
> `meeting.rtms_started` and `meeting.rtms_stopped`

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?

---

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [March 31, 2026, 6:54pm UTC](https://devforum.zoom.us/t/how-to-enable-rtms-for-my-account/142626/5 "2026-03-31T18:54:35Z")

</div>

@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.
