Overview
The Zoom API allows for alternative hosts to be added programmatically to meetings. This enables multiple people from a company to be able to become a host (in the event the host is unavailable to start a meeting).
I’m using the API to programatically create meetings with alternative hosts. This is my post request:
Everything seems fine: 201 response with the expected parameters on the response. On the Zoom admin area, the meeting is created and the alternative hosts set correctly.
The problem is that the alternative hosts don’t get the invitation email.
Am I missing any attribute on my request?
If I create the meeting via the web admin area with the same parameters and the same alternative hosts, they get the invitation email.
I’m going to add a bit more context here so maybe you can help me.
We call the API using a JWT token which comes from an app created on the app marketplace.
The API allow us to create meetings with a host and alternative hosts, both licensed users. The host can see the meeting created on his Zoom meetings area but the alternative hosts neither receive a notification nor can they see the meeting on their meetings area.
If we cancel the meeting via API then the alternative hosts receive a cancellation email which says that our main Zoom account, not the host account, has cancelled the meeting.
Thanks for taking the time to investigate this issue.
I believe I may know why my alternative hosts are not getting the notifications. The account I’m using to create the meetings, which is the same I used to create the marketplace app (where I get the JWT token from) is not the owner account, it’s an admin account.
It seems like the notifications configuration belongs to the owner account. So, when I change the meeting main host replacing: https://api.zoom.us/v2/users/me/meetings
with https://api.zoom.us/v2/myuser/admin_user_id/meetings
The email notification configuration is still inherited from the owner account. That means that, if the owner account has the notifications disabled, the meeting’s host notifications configuration doesn’t apply.
We got an issue in opposite way. We have turned OFF the alternative host email notification in both account level and user level. However, our users still received the email titled “You are no longer an alternative meeting host” if we removed the users from alternative by Zoom API. It won’t happen if we remove the alternative host in Zoom website.
Can you share your account ID and example of the API request you’re making when the email is triggered? I’m happy to take a closer look at this for you.
Our account number is. We used the update meeting API to remove the alternative hosts.
URL: {{baseUrl}}/meetings/:meetingId (PATCH)
Body: {“settings”: {“alternative_hosts”: “”}}
Thanks for confirming those details. In taking a look at your account, I can also confirm that your settings seem to correctly reflect having that notification off. As a next step, is it possible to forward us one of the email notifications to developersupport@zoom.us that the alternative host received? This should help us to take a closer look.