# Request to enable non-interactive batch token retrieval for CARE CAME (user-managed General App)

**URL:** <https://devforum.zoom.us/t/request-to-enable-non-interactive-batch-token-retrieval-for-care-came-user-managed-general-app/147380>\
**Category:** Authentication\
**Created:** [October 23, 2026, 2:26pm UTC](https://devforum.zoom.us/t/request-to-enable-non-interactive-batch-token-retrieval-for-care-came-user-managed-general-app/147380 "2026-10-23T14:26:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![came](https://avatars.discourse-cdn.com/v4/letter/c/b38774/32.png) [@came](https://devforum.zoom.us/u/came)\
**Post date:** [October 23, 2026, 2:26pm UTC](https://devforum.zoom.us/t/request-to-enable-non-interactive-batch-token-retrieval-for-care-came-user-managed-general-app/147380/1 "2026-10-23T14:26:25Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**

OAuth non-interactive authorization / batch token retrieval:

> **[Non-interactive authorization - Integrations - Zoom Developer Docs](https://developers.zoom.us/docs/integrations/non-interactive-auth/)**
>
> This article provides developer instructions for implementing OAuth 2.0 non-interactive authorization to enable Zoom applications to retrieve access tokens for multiple users in bulk without requiring individual user interaction.

**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:

1. Can it be enabled before Marketplace publication for Development/Local Test? What additional requirements apply to Production?

2. Which app/account identifiers, plans, permissions, scopes and review prerequisites are required?

3. After app enablement and the necessary distribution approval, can each customer administrator authorize their own users, or is separate customer enablement or allowlisting required?

4. How should newly added users/group members, scope changes and authorization withdrawal be handled?

5. 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

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [October 23, 2026, 2:29pm UTC](https://devforum.zoom.us/t/request-to-enable-non-interactive-batch-token-retrieval-for-care-came-user-managed-general-app/147380/2 "2026-10-23T14:29:44Z")

</div>

Hi @came  
Thanks for reaching out to us! I am happy to help here!

I can help you enabling this in your application and we can start by enabling this feature in your Development environment so you test it before going to production.  
The only requirement will be the app ID so we can enable it.

To answer your third question, each customer admin will be able to authorize their own users and there is NO seperate enablement or allowlist required.

For now, if new users are added to groups, you will need to reauthorize the app, but we are working on a mechanism to make this experience smoother.

And yes this flow can coexiste with your user-individual authorization path.

---

<div class="post-metadata">

**Author:** ![came](https://avatars.discourse-cdn.com/v4/letter/c/b38774/32.png) [@came](https://devforum.zoom.us/u/came)\
**Post date:** [October 24, 2026, 6:11pm UTC](https://devforum.zoom.us/t/request-to-enable-non-interactive-batch-token-retrieval-for-care-came-user-managed-general-app/147380/3 "2026-10-24T18:11:47Z")

</div>

Hi Elisa,

Thank you for your help and for clarifying the requirements.

Our app details are:  
App name: CARE CAME  
App ID: NWIn3dXJTqGYTW2dbehO3w  
App type: User-managed General App

Please enable non-interactive batch token retrieval for the Development environment first, as you suggested. We will test it before proceeding with Production.

Please let us know once it is enabled and whether any additional configuration is needed before testing.

Thank you!

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [October 26, 2026, 3:29pm UTC](https://devforum.zoom.us/t/request-to-enable-non-interactive-batch-token-retrieval-for-care-came-user-managed-general-app/147380/4 "2026-10-26T15:29:12Z")

</div>

Sure thing!  
I created this request for our team ( **ZSEE-217479** internal ticket number for reference) will update you when this is done

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [October 29, 2026, 1:19pm UTC](https://devforum.zoom.us/t/request-to-enable-non-interactive-batch-token-retrieval-for-care-came-user-managed-general-app/147380/5 "2026-10-29T13:19:13Z")

</div>

Hi @came  
Just to confirm this was enabled by out Engineering team and you should be able to implement this flow!
