Enable RTMS scopes for App ID V_PQgQamSqa8Igp_eIZywg (General App, User-Managed) — token has no rtms:* scopes

Realtime Media Streams
1

Hi Zoom team,

I’m building a meeting-transcription product and would like RTMS enabled for our app.

App

  • App ID: V_PQgQamSqa8Igp_eIZywg
  • Client ID: d7FURqGBRXuXvHLdjqluoQ
  • Type: General App, User-Managed
  • Mode: Development
  • WebSocket Event Subscription ID: pZy2dzLCQlK-_GXgr1r59g, subscribed to
    meeting.rtms_started and meeting.rtms_stopped

What already works

The outbound WebSocket connects and stays healthy. Against wss://ws.zoom.us/ws, a
client_credentials token mints (HTTP 200) and the connection is accepted:

{"module":"build_connection","success":true,"content":"success"}
{"module":"heartbeat","success":true,"content":"live"}

Heartbeats round-trip over holds of 45s and 120s.

What does not

No meeting event is ever pushed. I held the socket open through a real live meeting on
the developer’s own account and received 7 frames — all handshake and heartbeat, zero
events.

The cause looks like scopes. The access token’s scope list contains only these six, and
has never contained anything else:

marketplace:read:list_event_subscriptions
marketplace:write:event_subscription
marketplace:update:event_subscription
marketplace:delete:event_subscription
marketplace:update:client_secret
marketplace:write:websocket_connection

No rtms:* and no meeting:*. My reading is that marketplace:write:websocket_connection
alone buys the connection, which is why the socket is accepted while nothing about
meetings arrives. The console offers no way to add RTMS scopes, which is what brings me
here.

Request

Please enable the RTMS scopes for this app.

Intended use, so you can see the shape of it

  • Transcript only (media_type: 8). No raw audio subscription.
  • Arming automatically on join — not startRTMS() from the Zoom Apps SDK, and not
    the REST start endpoint. We have no embedded Zoom App.
  • Distribution target is Unlisted — reviewed, but not listed on the public
    Marketplace. Customers would install by direct link.

Two questions I’d rather resolve now than after review

  1. Is RTMS enablement per-app or per-installing-account? If every organisation that
    installs the app needs its own RTMS enablement request, self-serve onboarding isn’t
    possible and I need to design around that now.
  2. Must the meeting host’s account separately authorise the app for RTMS to start in
    a meeting that host owns? If the host must authorise, then meetings hosted outside the
    installing user’s account can’t be captured this way at all.

Thanks.

2

@Aris2 RTMS is already active on your account. You might be missing these 2 actions before you can receive the RTMS events.

  1. Auto starting of the application. Currently this is not enabled on your marketplace configuration
  2. Manual starting of the application via API.