RTMS error 2310 despite active Zoom Developer Pack

API and Webhooks
1

summary → Have tried using general app, s2s app and both in combo. have made the rtms app to auto start also.rtms does not ever auto start. it also cannot be started via api. whatever combo/scopes i setup.

my developer pack is ~500$ per month.

**details >

API Endpoint(s) and/or Zoom API Event(s)**

Description

We’re trying to start Realtime Media Streams (audio + transcript) in live meetings, following the RTMS REST API quickstart. Every start attempt fails with error 2310. Zoom’s auto-start for the app fails the same way: each attempt is followed by an rtms.request_status webhook with "status": 5, and meeting.rtms_started is never sent.

Support told us it’s a configuration error but couldn’t say which configuration. As far as we can tell, everything is set up:

  • RTMS app: General app, client ID 23KfoeEiRKerQyzbUXf0Q, still in development (not published), user-managed. RTMS feature enabled; scopes include meeting:update:participant_rtms_app_status, meeting:read:meeting_audio, meeting:read:meeting_transcript and rtms:read:*.
  • Token app: a Server-to-Server OAuth app in the same account, with meeting:update:participant_rtms_app_status:admin.
  • One account: the meetings, hosts and both apps are all in the same account (our master account).
  • Account settings: “Share realtime meeting content with apps” is on and unlocked. The General app is added under “Apps that access content in meetings”.
  • Auto-start: enabled on the app, for meetings users own and attend.
  • Webhooks: the endpoint is validated and receives signed events, including rtms.request_status.

Error?

HTTP 400
{"code":2310,"message":"Failed to perform RTMS app operation."}

Followed every time by:

{ "event": "rtms.request_status", "payload": { "operator_id": "<host user id>", "id_field": { "meeting_uuid": "<uuid>" }, "status": 5 } }

Tracking IDs (2026-10-23 UTC):

  • v=2.0;clid=aw1;rid=WEB_37d9eb0ec0017f4da58bd2bace5cc6ec: S2S token, 08:43:59
  • v=2.0;clid=aw1;rid=WEB_2173e1de90e0b875c5bff46b2aae4784: user token where the token user is the host, 07:33:30
  • v=2.0;clid=aw1;rid=WEB_0a5e3ca7bfebd23edfd3a4b396f3d53b: user token, a different host, 06:21:15

What we’ve ruled out. Other errors show up correctly when we test for them, which tells us the request gets past those checks:

  • S2S app’s own client_id in the body → 13262 “app is not authorized to access meeting content”. With the General app’s client_id (added to the allowlist), 2310 instead.
  • Every meeting was live with the host in it when we called.
  • Zoom’s own auto-start fails with status 5 about 1 second after the meeting starts, before we make any API call.

How To Reproduce

  1. Request:

    PATCH https://api.zoom.us/v2/live_meetings/{meetingId}/rtms_app/status
Authorization: Bearer <token>
Content-Type: application/json

{ "action": "start", "settings": { "client_id": "23KfoeEiRKerQyzbUXf0Q" } }

    {meetingId} is the numeric ID of a meeting in progress, taken from meeting.participant_joined.

  2. Authentication / app type:

    • Server-to-Server OAuth token (account_credentials) with meeting:update:participant_rtms_app_status:admin, or
    • a General app user OAuth token (authorization_code) for the meeting host with meeting:update:participant_rtms_app_status.

    Both give the same result.

  3. Error: 400 / 2310, then rtms.request_status status 5.

Questions

  1. Could a Zoom team member check the tracking IDs above and tell us which configuration causes 2310?
  2. Can a development (unpublished) General app start RTMS in its own account’s meetings, or does RTMS have to be enabled for the app (or the app published) first?

Thanks!

2

  • general app client id 23KfoeEiRKerQyzbUXf0Q [ removed from account for now ]

  • s2s app client id LbRS4_vGRdSy8dO_kcuQJg [ i had deactivated it for now ]

3

Hi @jitendra ,

I have raised this internally as you confirmed you purchased dev pack and are still getting this error. Waiting to hear back from one of my colleagues who can take a closer look. Thanks for raising this!