Hi Zoom Developer Support Team,
We are developing an integration using Zoom Real-Time Media Streams (RTMS) under our Zoom Developer Pack and Zoom Workplace Pro subscription.
During our concurrent meeting testing, we are consistently hitting a hard cap at 5 concurrent active streams. Whenever 5 streams are active, any subsequent call to start an RTMS stream fails with HTTP 400 and error code 2310 ("Failed to perform RTMS app operation.").
We confirmed this is neither an API rate limit nor a payload/auth issue:
- Rate limits are not being hit: Our API Dashboard shows the endpoint
/v2/live_meetings/{meetingId}/rtms_app/status_PATCHhas a 20.0 req/sec rate limit. We space our requests 4 to 6 seconds apart (~0.2 QPS), and none of the calls return HTTP 429. - Sequential/Solo calls succeed: Running meetings with host #6 or host #7 individually when 0 other streams are running succeeds immediately with HTTP 204.
- Hard 5-stream cutoff: Across repeated runs (Oct 29, Oct 30, and Nov 2), exactly 5 streams receive HTTP 204, and every stream beyond 5 receives HTTP 400.
Could you please inspect our account’s RTMS backend provisioning and increase our RTMS concurrent stream limit to 100 concurrent streams?
Account & App Context:
-
Account Plan: Zoom Workplace Pro + Zoom Developer Pack
-
S2S Client ID:
s3hVNKFzS5SxKOAYjiro5g -
Endpoint:
PATCH /v2/live_meetings/{meetingId}/rtms_app/status -
Payload:
{ "action": "start", "settings": { "client_id": "<USER_MANAGED_RTMS_APP_CLIENT_ID>", "participant_user_id": "<HOST_ZOOM_USER_ID>" } }
**Evidence from Zoom Marketplace Call Logs (Nov 2, 2026 UTC):
Full Sequence from this 15-Meeting Run (11:41 – 11:45 UTC):**
-
Streams 1–5: Succeeded with HTTP 204 (
action: "start"):- Meeting
82995966930(11:41:05 UTC) —204— TrackingId:WEB_9ff962f974b436a038afb38f612d9a6d - Meeting
84233626945(11:41:17 UTC) —204— TrackingId:WEB_b011364e5a1931bc32319cfcb82b7c9d - Meeting
82335733702(11:41:29 UTC) —204— TrackingId:WEB_76fdf218419c58aa8636e4c32c3c44b3 - Meeting
86997734806(11:41:47 UTC) —204— TrackingId:WEB_ac854ccde5e63357eeb7a1f77107134a - Meeting
89380493649(11:42:29 UTC) —204— TrackingId:WEB_45ab41046adcab0be871aafeda1e93d6
- Meeting
-
Streams 6–15: Failed with HTTP 400 Code 2310 (
action: "start"):- Meeting
87545587999(11:42:47 UTC) —400— TrackingId:WEB_c3400949fc30ee5473dda68ac035f768 - Meeting
85845084161(11:43:00 UTC) —400— TrackingId:WEB_224362ab1e892b27e441609017234e53 - Meeting
86412663888(11:43:11 UTC) —400— TrackingId:WEB_278d7e7130ed02a1f202d582f87eb0f5 - Meeting
88593561167(11:43:23 UTC) —400— TrackingId:WEB_10b1db29eb77a190bfd7a03a5797780b - Meeting
85747032603(11:44:03 UTC) —400— TrackingId:WEB_7188919f6859d70d5904b300d54439de - Meeting
82223600042(11:44:15 UTC) —400— TrackingId:WEB_e809564e429ff7a7bbcf2ff896dde87b - Meeting
84708570176(11:44:27 UTC) —400— TrackingId:WEB_a1a503ada60b67a3d5a3a316995fb1b7 - Meeting
84757427667(11:44:38 UTC) —400— TrackingId:WEB_bcf3cbd7bdfac49514cc0aa98eef3d57 - Meeting
88071918197(11:44:50 UTC) —400— TrackingId:WEB_a9d3c489920a9be5d3ea18d974408222 - Meeting
86843854823(11:45:14 UTC) —400— TrackingId:WEB_3b1087abdc6c941101b9c23be5fe0c57
- Meeting
Side-by-Side Marketplace Call Traces (Same Account, Same S2S App):
1. Successful Start (Stream #1 of 5 active, HTTP 204):
"root":{12 items
"urlPattern":string"https://api.zoom.us/v2/live_meetings/84246825060/rtms_app/status"
"time":string"1793626410258"
"status":int204
"method":string"PATCH"
"trackingId":string"WEB_ba250cfec0adfe371bad5357e21d2538"
"endPoint":string"https://api.zoom.us/v2/live_meetings/84246825060/rtms_app/status"
"responseHeaders":string"{}"
"requestParams":string"{}"
"requestHeaders":string"{<PII>}"
"requestBody":string"{"settings":{"participant_user_id":"yn-2XLdZTTC7FOHT7OJQKQ","client_id":"Mxxr8NPRTsyAOuvSxRs1A"},"action":"stop"}"
"httpStatus":string"204"
"response":string"N/A"
}
},
"response": "N/A"
}
2. Failed Start (Stream #6 attempted while 5 were active, HTTP 400 Code 2310):
"root":{12 items
"urlPattern":string"https://api.zoom.us/v2/live_meetings/87673635357/rtms_app/status"
"time":string"1793626343758"
"status":int400
"method":string"PATCH"
"trackingId":string"WEB_b235d202363febe1195f0f104cf28331"
"endPoint":string"https://api.zoom.us/v2/live_meetings/87673635357/rtms_app/status"
"responseHeaders":string"{}"
"requestParams":string"{}"
"requestHeaders":string"{<PII>}"
"requestBody":string"{"settings":{"participant_user_id":"9BZr9vATQs2VXA33X2Tp6w","client_id":"Mxxr8NPRTsyAOuvSxRs1A"},"action":"start"}"
"httpStatus":string"400"
"response":string"{"code":2310,"message":"Failed to perform RTMS app operation."}"
}
},
"response": {
"code": 2310,
"message": "Failed to perform RTMS app operation."
}
}
Current Dashboard Rate Limit Metrics:
- Endpoint:
/v2/live_meetings/{meetingId}/rtms_app/status_PATCH - Rate Limit:
20.0 requests/sec (medium) - Daily Limit:
999,999,999 - Calls in period:
396(Total Failures:357, all HTTP 400 when >5 streams active)
Please let us know once the concurrency pool on our account has been updated or if any additional information is required.
Thank you!