# Error to update schedule\_for for existing meeting

**URL:** <https://devforum.zoom.us/t/error-to-update-schedule-for-for-existing-meeting/69077>\
**Category:** Meetings\
**Created:** [May 16, 2022, 10:37pm UTC](https://devforum.zoom.us/t/error-to-update-schedule-for-for-existing-meeting/69077 "2022-05-16T22:37:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dpavlov](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@dpavlov](https://devforum.zoom.us/u/dpavlov)\
**Post date:** [May 16, 2022, 10:37pm UTC](https://devforum.zoom.us/t/error-to-update-schedule-for-for-existing-meeting/69077/1 "2022-05-16T22:37:13Z")

</div>

I’m getting error when try to update ‘schedule\_for’ for existing meeting. Error - {“code”:3000,“message”:“You cannot schedule a meeting for [user2@email.com](mailto:user2@email.com).”}

First, I create a meeting with payload:  
POST [https://api.zoom.us/v2/users/user1@email.com/meetings](https://api.zoom.us/v2/users/user1@email.com/meetings)  
{  
“topic”: “Topic for {useroneDisplayName}”,  
“type”: 2,  
“start\_time”: “{start:s}Z”,  
“timezone”: “UTC”,  
“password”: “password”,  
“duration”: {duration},  
“settings”: {  
“waiting\_room”: true,  
“approval\_type”: 2,  
“registrants\_email\_notification”: false,  
“registrants\_confirmation\_email”: false  
}  
}

Meeting was successfully created for user “[user1@email.com](mailto:user1@email.com)”.

Later, I’m updating this meeting:

PATCH [https://api.zoom.us/v2/meetings/{meetingId}](https://api.zoom.us/v2/meetings/%7BmeetingId%7D)  
{  
“schedule\_for” : “[user2@email.com](mailto:user2@email.com)”,  
“topic”: “Topic {usertwoDisplayName}”  
}

Request fails with error code {“code”:3000,“message”:“You cannot schedule a meeting for [user2@email.com](mailto:user2@email.com).”}

Both users: [user1@email.com](mailto:user1@email.com) and [user2@email.com](mailto:user2@email.com) are licensed users. Each can easily schedule a meeting.

Anything special should be done to update “schedule\_for” for the meeting?

---

<div class="post-metadata">

**Author:** ![dpavlov](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@dpavlov](https://devforum.zoom.us/u/dpavlov)\
**Post date:** [May 19, 2022, 1:52pm UTC](https://devforum.zoom.us/t/error-to-update-schedule-for-for-existing-meeting/69077/2 "2022-05-19T13:52:10Z")

</div>

Hi @elisa.zoom , last time you could quickly confirm what was the issue with adding registrants. Could you help with this issue please? Thanks!

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [July 1, 2022, 12:34am UTC](https://devforum.zoom.us/t/error-to-update-schedule-for-for-existing-meeting/69077/3 "2022-07-01T00:34:38Z")

</div>

Hi @dpavlov ,

Try referencing these post for possible programmatic solutions:

> [@Cannot update schedule\_for](https://devforum.zoom.us/t/cannot-update-schedule-for/69247/4):
>
> I think I had to call other way around: PATCH [https://api.zoom.us/v2/users/{user2@email.com}/assistants](https://api.zoom.us/v2/users/%7Buser2@email.com%7D/assistants) with payload: { “assistants”: [{ “email”: “user1@email.com” }] } Now it seems to work fine: topic and start\_url have been updated, meeting starts from user2 name.

> [@Changing the scheduled host for an existing meeting using the update\_meeting API?](https://devforum.zoom.us/t/changing-the-scheduled-host-for-an-existing-meeting-using-the-update-meeting-api/59343/12):
>
> My issue was that I was attempting to swap a host for an alternate in one step. It doesn’t work. What does is the following: Step 1. Save the alternate hosts and PATCH to clear { settings: { alternative\_hosts: ‘’ } } Step 2. Update the host for the new host email or id { schedule\_for: new\_host } Step 3. Modify the alternate hosts to ensure the new host is removed from the list and then PATCH { settings: { alternative\_hosts: new\_list\_without\_new\_host } } You must have schedule pr…

Thank you,  
Gianni
