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.
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."}
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.
{meetingId} is the numeric ID of a meeting in progress, taken from meeting.participant_joined.
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.
Error: 400 / 2310, then rtms.request_status status 5.
Questions
Could a Zoom team member check the tracking IDs above and tell us which configuration causes 2310?
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?
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!
I am able to do poc with rtms, need help in running in production.
we have 1000 sub users in parent account, want to selectively start RTMS transcript stream on few meetings.
there are 3 types of apps → s2s, user managed app, admin managed app
from experiment what I have gathered is
s2s app - this is needed to start RTMS via an api
admin managed app - this isnt useful, this keeps giving me this error
{“code”:13262,“message”:“The app ‘qtxW9AdfR8CVGJ7g8iIapA’ 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.”}
havnt found any place in zoom settings to be able to enable this/add this permission.
user managed app - for this need the app to be installed on every account. but even then RTMS doesnt start. the account with which s2s app was created needs to join the meeting else on calling start rtms api, I just get → rtms start meeting=93376242564 → 204 trackingid=v=2.0;clid=aw1;rid=WEB_69c2efe4050483a4fc975ef5ca2af36c, but no meeting.rtms_started webhook arrives
Please advise where I am going wrong. our requirement is want to auto start rtms for all users in a meeting in via api.
It only works with both s2s app activated and a user managed app installed in my account.
If I create a meeting via a child account, example: pankaj@myyogateacher.com the call to start rtms fails
if I add myself [ user who created s2s app ] as a cohost in the scheduled meeting via a child account, example: pankaj@myyogateacher.com and start meeting, webhook is never received. call gives 204 success, just that rtms doesnt actually start.
if I [ user who created the s2s app ] also join the meeting same meeting then only rtms started webhook/transcript starts to flow via webhook
We have a developer pack on our main account. Do I need to enable developer pack on all sub-accounts which will use RTMS feature, or will they share/use main account developer pack ?
also, enabling rtms will I get transcript of all spoken audio by all participants in meeting or only the user with Rtms user managed app?
can I not install centrally on parent account using Admin Managed Apps ?
@jitendra There are a few questions here, let me know if I missed out any.
You will need to propagate the license to your sub accounts for RTMS to work on your sub accounts. They can pay by master account.
When you enable transcript, you will get the transcript for all the users in the meeting.
RTMS for Meeting works only for User Managed App.
For the start meeting API to work, and if you are joining an external hosted meeting, you must be an invited participant.
Since this is a user managed app, either the user has to add it themselves, or the admin can add the users to the specific app. Goto App Marketplace , look for your application which has been created, clicking on it will show you similar page as shown below to “add users” to the RTMS app.
how do i propogate the license for rtms to work to sub-accounts/users? could you help with some steps on this.
for adding users to an app, is there some api that i can use to automate and bulk add users to the app? as these are dynamically created user accounts would want them to add them via api to app
these are all internal hosted meetings. our sub accounts are meeting hosts, external participants join meeting via invite links. will starting RTMS via api work in this case?
to be able to start RTMS via api do I need a S2S app? or i can do it via User Managed app itself ? basically which key/token is needed to start it
for your master-sub account, you can assign the licenses to the sub account . Managing Zoom sub accounts . If the sub account doesn’t work, ping me and let me take a look at the configuration
would utilizing user groups help you with the assignment of the RTMS apps to specific users?
Could you elaborate a bit on this? Sub accounts are meeting host, and there are participants who are joining this meeting. Are these participants invited in the scheduled meeting? Are you trying to start RTMS for the meeting host or for the invirtied participant?
If you want to start RTMS via API , you can use the user-managed app, but you will need the user to go thru the oauth request flow, in order for you call call the API with the user level access token
trackingid=v=2.0;clid=aw1;rid=WEB_69c2efe4050483a4fc975ef5ca2af36c, but no meeting.rtms_started webhook arrives