In the past I used time-limited developer access to RTMS which worked flawlessly. Recently, we purchased full RTMS access in our organisation, and now some communication seems to go amiss.
When auto-starting my RTMS app I get “connection failed” with no further information about the cause. All other communication between the Zoom and my backend seems to work with no issue: both the webhook validation and the OAuth callback work. What could be the cause of this issue?
I’d start with an app/account mismatch. Webhook validation and the OAuth callback only prove those two flows are working. They don’t prove the app selected for auto-start is the same General App that has RTMS event subscriptions and RTMS scopes enabled in the paid Zoom org. This is especially likely after moving from time-limited developer access to org-level RTMS access.
Two quick checks: In the Zoom app config, confirm the auto-start app is the same app whose webhook endpoint receives meeting.rtms_started. In your backend, confirm the RTMS client ID and secret loaded by the SDK are from that same app, since the RTMS SDK credentials are what the RTMS join path uses.
If those both match, capture the exact timestamp, meeting ID, app ID, and whether the meeting.rtms_started webhook arrived. If the webhook never arrives, this is more likely app entitlement, event subscription, or org enablement. If it arrives and the join fails, it is more likely credentials, payload handling, or SDK setup.
If you’re looking to use Zoom RTMS out-of-the-box, we’re a Zoom RTMS Preferred Partner. We’ve helped thousands of developers integrate with Zoom and can help you with your RTMS integration too!
@Jasper-TNG first thing i would suggest is to move out of ngrok for webhook and use a static URL for this. Most likely the issue is ngrok going offline. I’ll PM you to get more information if necessary
