ZAK Token related queries

Zoom Apps Meeting bots
1

1. Can we join the meetings using Meetings SDK as guest after 2nd March? Are there any restrictions in the Zoom Settings for this scenario?
2. How many concurrent meetings can a bot join using ZAK tokens?

Can the same ZAK token be used to join multiple concurrent meetings?
If not, would it be feasible to join multiple concurrent meetings by generating separate ZAK tokens (one per meeting)? What would the expected behavior be in that case?

Specifically, if I generate a new ZAK token and join a different meeting, will the bot that joined using the older ZAK token be forced to exit the existing meeting?

2

Hi @Harshal1, I highly suggest reading this Zoom Support Thread which highlights the changes coming to the Zoom DX

Can we join the meetings using Meetings SDK as guest after 2nd March? Are there any restrictions in the Zoom Settings for this scenario?

You can still join meetings using the Meeting SDK but your Zoom client will need to be identified through an OBF token or a ZAK token

How many concurrent meetings can a bot join using ZAK tokens?

Concurrency isn’t really a “ZAK limit” so much as a Zoom user/account concurrency limit: if your bot joins/hosts as a specific Zoom user, that user’s ability to run multiple meetings is governed by Zoom’s concurrent meeting rules (Hosting multiple meetings simultaneously). You should be aware that free Zoom accounts have a 2 meeting concurrency limit but there doesn’t seem to be a concurrency limit for paid Zoom accounts.

3

Thanks Amanda. That’s helpful.

I have some follow up queries as well

Currently, our app has the user:read:admin scope, and with this scope we are able to call the API:
GET /v2/users/{userId}/token?type=onbehalf&meeting_id={meeting_id} to fetch the OBF token.

However, the Zoom documentation mentions that the user:read:token scope should be added to the app.

My questions are:

  1. Will we still be able to generate the OBF token using the existing user:read:admin scope from March 2 onwards?

  2. Are user:read:admin and user:read:token treated as separate scopes? In other words, is user:read:token not implicitly covered under the broader user:read:admin scope?

  3. Will the current functionality of generating the OBF token with only the user:read:admin scope stop working after March 2?