This is the plan that I have:
For a Video SDK app, start with the Video SDK RTMS events, not the meeting events. Zoom lists session.rtms_started and session.rtms_stopped for Video SDK sessions, while meeting.rtms_started and meeting.rtms_stopped are for Zoom Meetings. The session event payload includes session_id, session_key, rtms_stream_id, and server_urls, which are the values your backend uses to connect to the RTMS stream.
In Marketplace, go through Develop → Build Video SDK and enable Event Subscriptions under the Video SDK app flow. If those RTMS session events are not shown there, the most likely blocker is entitlement or enablement, since Zoom says RTMS requires account-level enablement before you can configure the app. This is not something your webhook endpoint can fix.
Two checks: Confirm you are logged into the Marketplace with the same Video SDK account that owns the app. Then ask Zoom to verify RTMS is enabled for both your account and that specific Video SDK App ID or Client ID, and include a screenshot showing the missing RTMS event types.
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!
@James40 you mentioned that your video sdk accuont was created a while ago. For RTMS, you will need a universal credit account. I’ll PM you to get your details to check on this on the backend.