Hi Kamil,
We have customers running Zoom bots with ZAK tokens at scale, so I can help out with some of these questions!
-
Concurrent-meetings limit per ZAK / per user
We haven’t observed any concurrency limits with ZAK tokens, you should be able to use one single Zoom service account/user to generate all the ZAK’s for all meetings. You don’t need to worry about maintaining multiple service accounts to provide ZAK tokens to different meetings. -
Does generating a new ZAK invalidate the previous one?
Generating a new ZAK shouldn’t invalidate the previously-generated ZAK tokens. -
Impact of ZAK expiry while the bot is already in the meeting
You’re correct that the ZAK is checked at join time. If the ZAK expires after the bot has joined the meeting, it will not be ejected from the meeting. However, if your bot loses its connection with the meeting partway through and tries to rejoin, you’ll need to generate a fresh ZAK token for it to be able to join successfully. -
Name & avatar personalisation with ZAK
The behavior where the bot’s name is configurable while the bot’s profile picture is inherited from the underlying Zoom account has been consistent since we’ve started using ZAK tokens over two years ago, so I wouldn’t expect this to change any time soon.
Since a single service account user should be sufficient for your use case, I don’t think questions 5 and 6 will be relevant for you anymore.
Another option that you can consider would be the Recall.ai API. It’s a unified API that lets you send meeting bots to video conferencing platforms (like Zoom) to capture the audio and video in real-time. We also support providing ZAK tokens to Zoom bots. I’ll link our documentation for ZAK tokens here in case it’s helpful.
Let me know if you have any questions!