This usually points to missing account-side RTMS enablement, not a missed UI step. Zoom’s RTMS setup for meetings says you must first get RTMS enabled in your account, and Zoom’s forum thread on RTMS Account Access says access starts with a 30-day trial request and then explicit enablement by Zoom. So the “Allow apps to access meeting content” and auto-start toggles are necessary, but they do not replace the backend entitlement.
Your PATCH /v2/live_meetings/{meetingId}/rtms_app/status call and the meeting:update:participant_rtms_app_status scope look correct, but those alone don’t prove the app is allowed to access meeting content. One more gotcha from Zoom’s RTMS forum guidance is environment: if you are testing the production version of the app, unpublished production apps can fail even when dev is configured correctly.
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!