Two meeting.rtms_started webhooks fire per meeting

Realtime Media Streams
1

Hi guys I have a problem with our RTMS setup: every time a meeting starts, our backend receives two separate meeting.rtms_started webhook payloads for the same meeting_uuid. Each has a different rtms_stream_id. One stream handshakes successfully using our RTMS app credentials. The other consistently returns status_code: 3 (Invalid signature), meaning its stream was created by a different app whose credentials we don’t have.

Therefore TWO identical apps are appearing in our Zoom calls, the first one is stopped but able to be started (It is programmed to start automatically so this is no good) and the second can’t be started.

Screenshot 2026-06-03 at 10.26.08 pm
Screenshot 2026-06-03 at 10.26.08 pm250×162 26.9 KB

Here’s what’s happening in a call from today:

Stream 1: rtms_stream_id=53bc85049d864966a3d94dc35b636cbb - Handshake: FAIL status_code=3 “Invalid signature”

Stream 2: rtms_stream_id=f5e65fd40bb940369573e64428eb5711 (760ms later) - Handshake: OK

We have two apps - one does NOT have any RTMS scopes enabled, never has.

Can somebody help identify what in our account could be triggering a second RTMS stream?

We don’t have records of any changes made to any Zoom apps around May 4th when this started happening.

The app ID is bpzT8tG7Rcinq7q6trHmkQ

2

@BrianCassingena I’ve just checked your account, this is probably due to production and development environment having the same event subscription endpoint.

One of the expects the production credentials, and the other one expects development credential. Hence this explains why one of them fails and the other one succeed, and why both of them have the same identical app name.

3

Thanks @chunsiong.zoom that was the problem. I found the UI counterintuitive in that I thought I had to change the ‘setting’ of the app from dev to production but I see how it works now. Problem solved, thanks for helping, all fixed now.