RTMS returning 400 inspite being enable from zoom side to my acct

Video SDK
1

We are testing Zoom RTMS for live meeting audio streaming.

We verified the following:

S2S token works successfully.
GET /v2/meetings/97099264422 returns 200.
Meeting host is academy@ajantapharma.com.
Meeting host_id, academy user_id, and participant_user_id all match:
Y3rXWt4hRsGF-70xawvrUg

We also tested our webhook by sending a fake meeting.rtms_started event, and it correctly saved the RTMS payload.

But when we call the official RTMS start API:

PATCH /v2/live_meetings/97099264422/rtms_app/status

Payload:
{
“action”: “start”,
“settings”: {
“client_id”: “aZH6ibw6TpWVmGqphtvOpw”
}
}

We get:

400
{“code”:2310,“message”:“Failed to perform RTMS app operation.”}

We also tested:
client_id + protocol=webhook
client_id + participant_user_id
client_id + participant_user_id + protocol=webhook

All return the same 2310 error.

No real meeting.rtms_started webhook is received.

Can you please confirm why RTMS start is being rejected for this app/account/meeting, and whether RTMS is fully enabled/provisioned for this Zoom account and app?

2

Important context: earlier, we were able to connect to the RTMS signaling WebSocket using an existing RTMS payload containing meeting_uuid, rtms_stream_id, and server_urls. So our RTMS receiver/join side was able to connect when a valid RTMS payload was available.

But now, for the current live meeting, Zoom is not generating a fresh RTMS payload because the RTMS start API is failing.

3

@akash9 your trial has expired on 22nd June 2026. please sign up for a developer pack here https://zoom.us/pricing/developer

4

thank you for the reply and helping me out