# Rebuilding Zoom App: Mapping API Calls to Granular Scopes

**URL:** <https://devforum.zoom.us/t/rebuilding-zoom-app-mapping-api-calls-to-granular-scopes/134333>\
**Category:** Meeting SDK\
**Created:** [June 23, 2025, 9:13am UTC](https://devforum.zoom.us/t/rebuilding-zoom-app-mapping-api-calls-to-granular-scopes/134333 "2025-06-23T09:13:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Concilium](https://avatars.discourse-cdn.com/v4/letter/c/e0b2c6/32.png) [@Concilium](https://devforum.zoom.us/u/Concilium)\
**Post date:** [June 23, 2025, 9:13am UTC](https://devforum.zoom.us/t/rebuilding-zoom-app-mapping-api-calls-to-granular-scopes/134333/1 "2025-06-23T09:13:08Z")

</div>

**Hi everyone,**

I’m in the process of rebuilding a Zoom local app on a new tenant, and I noticed that Zoom now uses more granular scopes for API access permissions.

Given that my original app interacts with various Zoom APIs, I was wondering:

**Is there an efficient way to determine which granular scopes are required based on the API calls my app makes?**

Ideally, I’d like to avoid manually matching each endpoint with its corresponding scope from the documentation. Is there a tool, best practice, or even a logging/debug method that could help infer or list the necessary scopes based on actual API usage?

Thanks in advance for your help!
