Currently the RTMS media scope and webhook events are not available to our account:
The scope rtms:read:meeting_audio:admin does not appear under Add Scopes > RTMS (only notification scopes such as rtms:read:rtms_concurrency_limited:admin are listed).
The events meeting.rtms_started and meeting.rtms_stopped do not appear in our Event Types list.
Please enable RTMS for Meetings for this account so we can request the rtms:read:meeting_audio:admin scope and subscribe to the meeting.rtms_started / meeting.rtms_stopped webhook events.
Use case: We are a meeting transcription & summary product. With user consent via OAuth, we consume per-participant meeting audio through RTMS and transcribe it with our own speech engine to produce Hebrew transcripts and summaries. We need audio only (no video, no Zoom transcript). Our webhook endpoint at app.wiss.co.il is already implemented and passes URL validation.
@Adir1 we are no longer providing trial over the developer forum. We have now transitioned to a self-service method. You can sign up for the developer pack here
Hi @chunsiong.zoom, thanks for getting back to me. I signed up for the pay-as-you-go developer plan like you suggested.
Something did change after that - a Meetings category now shows up under Add Scopes, which wasn’t there before. But I still can’t find the rtms:read:meeting_audio scope anywhere. The only RTMS stuff I can actually add are the event scopes (concurrency_limited, concurrency_near_limit, interrupted) and the Contact Center / ZCC Voice ones. Under Meetings the only thing is meeting:update:participant_rtms_app_status. No meeting audio scope at all.
Is there normally a delay before it shows up after subscribing, or should it be there right away? And could this be because my app is Admin-managed? The RTMS feature in the Surface tab says it’s only for User-managed apps, and the switch to User-managed is locked on my existing app. If I just need to spin up a separate User-managed app, happy to do that - just want to make sure I’m going down the right path before I rebuild anything.
Got it, thanks @chunsiong.zoom - so it has to be a General OAuth app that’s User-managed.
Quick thing before I rebuild: my existing app is a published Admin-managed app (it already handles calendar + meeting list and has live users). Can I just create a brand new User-managed General app purely for the RTMS audio side and run the two side by side, or do you recommend migrating everything into one new User-managed app? Mainly trying to avoid breaking the current integration for existing users.
@Adir1 the scope for user and admin managed app can be different, and I’m not certain if user admin app might have the same scope which you need from your existing admin managed app.
It might make sense to consolidate if the scopes can cover what you currenly use on your admin managed app.