Linux Meeting SDK 7.1.5.4432, x86_64. New user-managed General App in Development, Meeting SDK enabled, bot/AI-notetaker declared, OAuth PKCE with only user:read:token.
Intended use
We are developing WIIN Recorder, a clearly named, visible recording participant invited by a consenting customer to a Zoom Meeting. The host must explicitly grant recording permission. We do not want to bypass waiting rooms, authentication, consent, or app review. The target includes meetings hosted on Zoom Basic/free accounts; cloud recording is not the intended route.
In our own isolated free test account, an OBF-authorized native SDK participant joined and captured mixed raw audio after the desktop host personally granted recording permission. This establishes only technical feasibility in our own Development test, not production eligibility or permission to serve other accounts. No customer recordings, tokens, meeting links, or credentials are included here.
Policy clarification requested
The Linux SDK documentation says it is designed for human use cases, that bots/AI notetakers are not supported, and recommends RTMS:
The OBF FAQ and authentication guidance also describe notetaker attribution and external-meeting review:
Could Zoom staff clarify:
Can a new app obtain approval today for this visible, host-consented Linux SDK recording participant, or is this route limited to previously approved/legacy notetakers? If allowed, what exact review/approval route applies (including an unlisted integration)?
For external-account meetings, which user must authorize and remain present for OBF, and what must happen when that user leaves? Are Basic hosts eligible, and is any paid host plan, developer entitlement, or raw-recording licence required?
If new recording bots must instead use RTMS, can a customer with only a Basic/free Zoom host account authorize it? Which party must hold the developer entitlement and pay usage, and can it support the same host-consented recording/transcription use case without cloud recording?
We are not asking for an exception or a way around restrictions. We need the supported architecture and eligibility requirements before enabling a production integration. Thank you.
To clarify the intended distribution: one centrally operated General App with Meeting SDK, not a separate developer application for every customer. Each customer would authorize that common app once via Zoom OAuth, then supply a meeting link. The meeting may be hosted by a different Zoom account. The recorder would be a visible participant, respect admission/security settings, request the host’s recording permission and display the required recording notice.
Could Zoom staff confirm:
Is this common-app model eligible for a newly developed Linux SDK recording/notetaker app today? What review/entitlement route applies to listed or unlisted distribution?
For an externally hosted meeting, can an OAuth-authorized customer who is present supply the OBF attribution while a host who has not installed the app independently approves entry and recording?
If that authorized customer is absent or leaves, is there any supported SDK route based solely on the external host’s admission and recording consent, without that host authorizing the app? If not, please confirm that limitation explicitly.
Does this support independent Basic/free host accounts, and are any paid SDK/raw-recording entitlements required beyond the host’s recording controls?
We are asking about the supported permission and review path, not a bypass. Real deployment remains disabled pending clarification.
For a new app, I would not build the production architecture around the Linux Meeting SDK recorder participant. Zoom’s Linux Meeting SDK usage policy says the SDK is for human use cases, does not support bots or AI notetakers, and directs those workloads to RTMS. The OBF FAQ’s allowance for continued Meeting SDK operation is specifically framed around legacy note-taking apps. I don’t see a documented review path that overrides that policy for a newly created recorder bot, including an unlisted app.
For external meetings, the OBF requirements are clearer. The OAuth-authorized Zoom user must already be present before the SDK participant joins. The OBF token is tied to that user, and if they leave, the SDK session ends and must rejoin using another authorized user’s token.
For RTMS, Zoom currently documents that it provides live audio, video, and transcript data without requiring cloud recording, but its plan compatibility guidance says Basic accounts are not supported and that paid plans require Zoom Developer Pack entitlement. That makes the Basic-host requirement the main blocker to confirm with Zoom before committing to RTMS.
Recall.ai is a Zoom RTMS Preferred Partner, and you can get further RTMS implementation support through Recall.ai if useful.