Cannot update schedule_for

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.”}

First, I create a meeting with payload:
POST 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”.

Later, I’m updating this meeting:

PATCH https://api.zoom.us/v2/meetings/{meetingId}
{
“schedule_for” : “user2@email.com”,
“topic”: “Topic {usertwoDisplayName}”
}

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

Both users: user1@email.com and user2@email.com are licensed users. Each can easily schedule a meeting.

Anything special should be done to update “schedule_for” for the meeting?

Hi @dpavlov

Can you please make sure that you have assigned Schedule Privileges to the users in order for you to be able to use the field “schedule_for”

Learn more about that topic here:

Best,
Elisa

Tried to research around this a little bit.

I could successfully add assistant (user2) to account of user1
PATCH https://api.zoom.us/v2/users/{user1@email.com}/assistants with payload:
{
“assistants”: [
{
“email”: “user2@email.com
}
]
}

Call GET https://api.zoom.us/v2/users/{user1@email.com}/assistants correctly shows
{“assistants”:[{“id":“b65d4XDvQXSzywWqm2pGBQ”,“email”:"user2@email.com”}]}

I’m trying to patch meeting again:

PATCH [https://api.zoom.us/v2/meetings/{meetingId}]
{
“schedule_for” : “user2@email.com”,
“topic”: “Topic for {usertwoDisplayName}”
}

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

Anything else should be set to update schedule_for property?

Thank you!

I think I had to call other way around:

PATCH https://api.zoom.us/v2/users/{user2@email.com}/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.

Hey @dpavlov
Happy to hear you got a workaround via API!
I also would encourage you to take a look a this guide, to allow scheduling privileges to users in your account

Thanks!
Elisa

1 Like

We programmatically create/remove/manage users. It would be not ideal to go to Zoom Portal and assign privileges manually. I read your link and it helped a lot to understand root cause of our issues and find needed API to assign assistants. Thanks again!

1 Like

Of course! @dpavlov happy to help :slight_smile:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.