Meeting SDK use for on-premise per-tenant meeting capture

Meeting SDK
1

We are building an on-premise, per-tenant meeting capture system. Each deployment runs under the customer’s own Zoom account. The bot is created, owned, and operated by the customer on their own account. It joins only meetings hosted within that same account/org.

We intend to use the Zoom Meeting SDK for Linux to capture real-time audio per participant. Before committing to the build, we want to confirm:

Under this deployment model (bot running on the customer’s own account, joining their own meetings) is the Meeting SDK the correct and permitted path? Or does our use case require a separate agreement with Zoom?

We understand the March 2, 2026 mandate requires OBF/ZAK or RTMS for cross-account meeting access. For meetings hosted within the same account/organization, which auth flow applies? We want to ensure we are compliant with your terms before choosing a certain path, not after.

2

The same-account distinction only affects the additional authorization requirement. Zoom’s March 2, 2026 authorization change does not require OBF or ZAK for meetings hosted under the same account as the app’s client ID. It does not override the bot usage policy. RTMS is the documented path for automated capture, and it supports separate participant audio streams as well as merged audio.

A customer-owned RTMS app can be configured per tenant, but Zoom requires Developer Pack credits and the relevant app, scope, event, and account settings described in the RTMS meeting requirements.

Recall.ai is a Zoom RTMS Preferred Partner, and further implementation support is available through us.