# Accessing AlternativeHost/SchedulingFor feature through API

**URL:** <https://devforum.zoom.us/t/accessing-alternativehost-schedulingfor-feature-through-api/16416>\
**Category:** API and Webhooks\
**Created:** [May 6, 2020, 2:58pm UTC](https://devforum.zoom.us/t/accessing-alternativehost-schedulingfor-feature-through-api/16416 "2020-05-06T14:58:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![integrationAnywhere](https://avatars.discourse-cdn.com/v4/letter/i/e99b99/32.png) [@integrationAnywhere](https://devforum.zoom.us/u/integrationAnywhere)\
**Post date:** [May 6, 2020, 2:58pm UTC](https://devforum.zoom.us/t/accessing-alternativehost-schedulingfor-feature-through-api/16416/1 "2020-05-06T14:58:12Z")

</div>

**Description**  
We need to provide alternative hosts and scheduling for options in our case. We are unable to confirm this in our test account. We are having a pro account for testing. We are having another user with the basic plan. We try to create a meeting with the newly added user as an alternative-host. It’s not working as expected. It’s expecting the new user also to have a paid pro account.

Is there any other way to test this for the developer accounts, without having another pro user account? If it is not possible, can we have a confirmation on this in an elaborated way?

We need to know and confirm, whether alternativeHost feature will work if we add licensed user in meeting payload, as “schedule\_for”: “user email”.

**Error**  
When we try to have a “schedule\_for” parameter with the newly added user in meeting payload, we got the below error.  
{  
“code”: 1110,  
“message”: “Not assigned scheduler.”  
}

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
We are developing account Level OAuth app

**Which Endpoint/s?**  
[https://api.zoom.us/v2/users/me/meetings](https://api.zoom.us/v2/users/me/meetings)

**Additional context**  
It will be helpful if there is an exemption in accessing these features in developing phase of the developer app.

---

<div class="post-metadata">

**Author:** ![samly](https://avatars.discourse-cdn.com/v4/letter/s/a87d85/32.png) [@samly](https://devforum.zoom.us/u/samly)\
**Post date:** [May 6, 2020, 5:28pm UTC](https://devforum.zoom.us/t/accessing-alternativehost-schedulingfor-feature-through-api/16416/2 "2020-05-06T17:28:40Z")

</div>

For “schedule for” to work, you would need to add the pro user as an “assistant” to the basic user.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [May 12, 2020, 6:05am UTC](https://devforum.zoom.us/t/accessing-alternativehost-schedulingfor-feature-through-api/16416/3 "2020-05-12T06:05:43Z")

</div>

Hey @integrationAnywhere,

Please see the prerequisites for the schedule\_for and alternative\_host features here:

> **[Scheduling privilege](https://support.zoom.us/hc/en-us/articles/201362803-Scheduling-privilege)**
>
> Overview
> Scheduling privilege is designed for a user or an executive admin to:
> 
> You can assign or delegate a user or multiple users in your account to schedule meetings on your behalf. 
> You can als...

> **[Alternative host](https://support.zoom.us/hc/en-us/articles/208220166-Alternative-host)**
>
> Overview
> The alternative host option allows you to schedule meetings and designate another Licensed user on the same account to start the meeting on the host's behalf. This user will receive an ema...

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 9:15pm UTC](https://devforum.zoom.us/t/accessing-alternativehost-schedulingfor-feature-through-api/16416/4 "2020-08-21T21:15:38Z")

</div>