Alternative hosts are not notified

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:

curl --request POST \
  --url '[host_email]/meetings?=' \
  --header 'authorization: Bearer [token]' \
  --header 'content-type: application/json' \
  --data '{
  "topic": "Testing alternative hosts",
  "type": 2,
  "start_time": "2020-07-13T18:30:00Z",
  "duration": 0,
  "password": "[password]",
  "settings": {
		"host_video": true,
		"participant_video": true,
		"alternative_hosts": "[alternative_host_email]",
		"mute_upon_entry": false,
		"waiting_room": false

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.

Thank you in advance.

Hey @pvicente,

Make sure your Alternative Host Email Notification setting is turned on:


The Alternative Host Email Notification setting is turned on for the host user but the alternative hosts don’t get the email notification


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.


Hey @pvicente,

I am not able to reproduce this issue. With the following request body payload, I am getting an email sent to my alternative host:


  "topic":"Alternative Host Email Test",
  "settings": {
    "alternative_hosts": ""


Hi @tommy,

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:

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.

Does this make sense to you?


Hey @pvicente,

Correct. If your account admin/owner has disabled the email notification settings at the account level and locked it, then it will not send.