We created a sub-optimal solution to the topic shown below (which is still unresolved, and recently updated).
We are now using an Account Level Webhook Only app to send meeting.started and meeting.ended to our webhook consumer, which then (optionally) requests (via StoS app) to start RTMS for the meeting.
We discovered that the user’s “Primary Group” had to be added to our RTMS app, to allow that RTMS start request to succeed, vs getting (403) Forbidden.
It allows us to generate the necessary meeting events, and to trigger the RTMS events, without adding individual user accounts to any of our apps.
I call this solution sub-optimal, because the account level app covers everyone.
Is there any (creative) way to disable / remove / exclude a specific user account from receiving webhook calls from my Account Level Webhook Only app?
My goal is to separate a few user accounts that I will use to test against my local development environment (vs our Staging platform).
Zoom doesn’t appear to expose a per-user “exclude” switch for an existing account-level webhook subscription. For meeting.started and meeting.ended events, the cleanest workaround is to treat the account-level webhook as the broad signal and filter in your consumer by host/user ID before you call RTMS. That keeps your Staging path safe, but it won’t reduce Zoom’s outbound webhook volume.
The more “Zoom-native” option is to stop using one broad account-level subscription for this flow and create narrower subscriptions instead. Zoom’s Event Subscription API supports programmatic subscription management, and Create an event subscription includes user-scoped inputs such as subscription scope and user IDs. Use Get User or Account Event Subscriptions to verify what Zoom has actually subscribed. That is different from excluding one user from a single account-scoped subscription.
For RTMS-specific integrations, Recall.ai is a Zoom RTMS Preferred Partner and can help manage your RTMS integration too.