RTMS Webhooks Not Being Delivered & Subscription Validation Issue (User-Managed General App)

API and Webhooks
1

Hello,

We are currently building an RTMS integration for our company . Our account has an active RTMS Pay As You Go subscription (effective date: 15 Oct 2026).

We have set up a user-managed General App on the Marketplace, and our application side seems to be ready. However, we are facing an issue where Zoom RTMS webhooks are not reaching our endpoint at all.

Here are our app details:

  • Client ID: [REDACTED] (Can provide via DM)

  • Event Subscription URL: https://[REDACTED][.trycloudflare.com/webhook](https://.trycloudflare.com/webhook) (HTTPS, public)

  • Subscribed Events: meeting.rtms_started, meeting.rtms_stopped, and other relevant RTMS events.

  • Scopes (Verified in token): meeting:read:meeting_audio, meeting:update:participant_rtms_app_status

  • OAuth: User OAuth is fully completed and tested in a live meeting as the host.

Our Observations during testing:

  1. Calling PATCH /v2/live_meetings/{meetingId}/rtms_app/status with action=start returns HTTP 204 (Success).

  2. The app permission pop-up successfully appears in the live meeting.

  3. Despite this, the meeting.rtms_started webhook never arrives (our endpoint logs show no POST request from Zoom).

  4. When we call action=stop for the same meeting, we receive error 13277: “RTMS app has not been started”, which implies the stream never actually started in the backend.

  5. Our endpoint is publicly accessible and successfully returns a 200 OK for our own manual CRC URL validation tests. However, we noticed that when saving the Event Subscription in the Marketplace portal, the CRC validation request from Zoom doesn’t seem to hit our endpoint either.

  6. In the Marketplace, under the “Auto-start for RTMS apps” section, we see this warning: “This feature is not available based on your product selection.” (We are using the REST API to start it manually, but we suspect this might be related to our product entitlement).

Could you please help us with the following?

  1. Entitlement Check: Verify if the RTMS entitlement is genuinely enabled on the backend for this Account / Client ID.

  2. Webhook Logs: Check if the Event Subscription is fully active and investigate the webhook delivery / event logs to see why the payloads (and the CRC validation during save) aren’t reaching our URL.

  3. Product Selection Warning: Clarify why we are still seeing the “product selection” warning for Auto-start despite having an active RTMS Pay As You Go subscription.

  4. Enablement: If required, could you manually enable RTMS for this specific app from your side?

Thank you in advance for your help!

2

@Cagatay I’ve checked your account, RTMS is enabled. Can you try to regenerate your authorization url and add the app again? This will update your webhook endpoint to the latest ones. Tag me if this still doesn’t work

3

Hi,

I have granted the RTMS permissions on the Surface platform. Upon regenerating the authorization URL and re-adding the application, I re-approved the required permissions, which resolved the issue. Everything is now functioning as expected. Thank you for your assistance .