General App RTMS error 13262: "not authorized to access meeting content" despite completing all UI setup steps

Realtime Media Streams
1

Hello,

We are configuring a Zoom General App with Realtime Media Streams (RTMS) for meetings.

Current situation:

  • The app is a General App
    • RTMS-related scopes were added, including:
      • meeting:read:meeting_audio
        • meeting:update:participant_rtms_app_status
          • RTMS event scopes (rtms_started, rtms_stopped)
            • Event Subscription is configured and our webhook endpoint responds successfully
              • The app is added under Apps on account
                • It is assigned to user hello@chapelier.ru
                  • Auto-start is enabled
                    • In Zoom account settings under: Zoom Apps → Meetings → Auto-start apps that access shared real-time meeting content — the app appears and is enabled
                    • However, when we call:
                  • PATCH /v2/live_meetings/{meetingId}/rtms_app/status
                • with:
              • {“action”:”start”,”settings”:{“client_id”:”<GENERAL_APP_CLIENT_ID>”}}
          • Zoom still returns:
      • {“code”:13262,”message”:”The app ‘<CLIENT_ID>’ is not authorized to access meeting content. Please add it in the Allow apps to access meeting content setting in the Settings page of the Zoom web portal.”}
  • We have already completed the UI steps for “Allow apps to access meeting content” and the app is visible and enabled there.

Questions:

  1. Is there any additional backend entitlement, approval, or propagation step required for RTMS meeting content access?
  2. Is the app configuration missing any required RTMS capability beyond the scopes and auto-start settings?
  3. Is this expected behavior for newly configured RTMS apps, and if so, how long does propagation usually take?
  4. Are there any additional app type or publication requirements for using PATCH /live_meetings/{meetingId}/rtms_app/status with a General App?

Thank you.

2
Hi @apilsen,

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!

3

@apilsen you will need to activate RTMS on your account before it can be utilized. I’ve enabled a free trial on your account until 31st May. Let me know if you are still seeing the same error

4

Hi!
Thanks — RTMS trial is now active, but we are still seeing the issue.

Current behavior:
• the app appears in the meeting
• meeting.rtms_started webhook is received successfully
• our backend connects to the RTMS signaling server
• however, the signaling handshake is rejected
• the handshake response returns status_code=3
• then Zoom sends meeting.rtms_stopped with stop_reason=18

So the issue is no longer just account activation — the RTMS session still cannot proceed past signaling.

Could you please clarify:

  1. what status_code=3 means for the RTMS signaling handshake
  2. what stop_reason=18 means in this flow
  3. whether there are any additional backend permissions or updated handshake requirements for General App RTMS sessions

If needed, I can also provide exact webhook payloads and logs.

5

@apilsen you using the SDK or following our rtms-samples on github? Could you share the payload you are using to connect to the signaling server?