Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI CompanionUser groups are unique spaces where community members can collaborate, network, and exchange knowledge on similar interests and expertise.
Help & Resources is your place to discover helpful Zoom support resources, browse Zoom Community how-to documentation, and stay updated on community announcements.
The Events page is your destination for upcoming webinars, platform training sessions, targeted user events, and more. Stay updated on opportunities to enhance your skills and connect with fellow Zoom users.
2021-07-16 05:12 AM
Hi,
When I create a meeting and enter approval_type = 0 it always returns approval_type=2. It´s a paid account. Here's the json sent and returned:
Sent Json:
I've seen several cases that occur in the same way. The PMI parameter for schedule meeting is disabled too.
The goal is to control access to meetings.
The test are made using postman with the parameters:
url: users/me/meetings
post
JWT Bearer.
Tks.
Solved! Go to Solution.
2021-07-16 09:57 AM
MarcusPaulo, welcome to the community!
I believe that the issue is related to the fact that you are using the "me" parameter with a JWT call. Since the JWT token is account wide, it would not necessarily know which user you are trying to schedule the meeting for (and that they are licensed). Could you please retry the call using the email address of the user instead of "me" and let us know if that changes anything?
Thanks.
2021-07-16 09:57 AM
MarcusPaulo, welcome to the community!
I believe that the issue is related to the fact that you are using the "me" parameter with a JWT call. Since the JWT token is account wide, it would not necessarily know which user you are trying to schedule the meeting for (and that they are licensed). Could you please retry the call using the email address of the user instead of "me" and let us know if that changes anything?
Thanks.
2021-07-19 08:51 AM
Thank you @colegs !