Rebuilding Zoom App: Mapping API Calls to Granular Scopes

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!