API Endpoint(s) and/or Zoom API Event(s)
OAuth non-interactive authorization / batch token retrieval:
Description
Hello Zoom Developer Support,
Following Step 1 of the documentation above, we would like to request non-interactive batch token retrieval enablement for our existing CARE CAME app.
CARE CAME is an Android remote field-support product using the Zoom Meeting SDK and a server backend, developed by 株式会社ASTER (ASTER) in Japan.
We plan to serve multiple independent customer organizations. Each customer’s Zoom administrator would authorize selected employees or groups in advance. Employees would then sign in to CARE CAME using their company Google identity, with their individual Zoom connection prepared through administrator authorization. Google Calendar consent would be handled separately where required.
Could you enable this capability for our existing app, or advise the required process? Please clarify:
-
Can it be enabled before Marketplace publication for Development/Local Test? What additional requirements apply to Production?
-
Which app/account identifiers, plans, permissions, scopes and review prerequisites are required?
-
After app enablement and the necessary distribution approval, can each customer administrator authorize their own users, or is separate customer enablement or allowlisting required?
-
How should newly added users/group members, scope changes and authorization withdrawal be handled?
-
Can this flow coexist with our existing individual Zoom authorization path?
We are preparing the bulk authorization implementation and would like to confirm these prerequisites before testing. We will maintain separation between customer organizations and verified user identities, and will not overwrite existing users’ licenses during initial linking.
App name: CARE CAME (formerly General