Meeting.rtms_started webhook missing WebSocket URL / Stream ID

API and Webhooks Authentication
1

Hi Team,
Our RTMS-enabled Zoom App previously received full RTMS session details in the meeting.rtms_started webhook, including:

  • server_urls

  • rtms_stream_id

  • signature / access token

Recently, the webhook only returns the event name and meeting_uuid, and all RTMS connection fields are missing. Because of this, we are unable to create RTMS records or connect to the RTMS WebSocket.

This behavior worked earlier with the same configuration and is now consistently reproducible.

Environment:

  • Web SDK v3.12.0

  • Salesforce (Visualforce + LWC)

  • RTMS App from Marketplace

  • Event: meeting.rtms_started

Questions:

  1. Has RTMS Webhook payload behavior changed?

  2. Is WebSocket mode now required to receive RTMS session details?

  3. Is this related to license or RTMS app configuration?

Thanks for your support.

2

The RTMS meeting.rtms_started webhook is expected to include the connection details (server_urls, rtms_stream_id, and signature) under the nested payload.payload object. If your handler is only looking at the outer wrapper, you can end up logging just event plus whatever fields you happen to surface

Also make sure you’re correctly handling Zoom’s webhook validation ping: when the request includes the x-zoom-webhook-validator header you must echo plainToken, and only treat real POST bodies as RTMS events

If parsing/validation is correct and the RTMS fields are genuinely absent, it usually points to account/user enablement: RTMS access can be toggled by Zoom (see a real example where support enabled a trial in the forum thread on missing RTMS events/scopes)

3

Hi @harkunal - I am going to DM you - I have a feeling your free trial of RTMS may have expired.