Hi @harald.schmid - I recently had to use schedule_for
as a workaround when I accidentally created ~60 meetings under only one host. (oops )
Before you can do this, you have to assign scheduling rights for each userID.
For the end user you want the meeting to be assigned to, add your Admin userID as an assistant of the through the Assistant API. You’ll want to add the admin as an assistant of the current alternative host, which will allow you to edit the meeting to change them to host.
POST
/users/{ALTERNATIVE HOST USER ID}/assistants
// request body:
{
"assistants": [
{
"id": "{ADMIN_USERID}",
"email": "{ADMIN_EMAIL}"
}
]
}
Then, use the Update Meeting API to add the alternative host of the meeting in the schedule_for
value.
PATCH /meetings/{meetingId}
// request body
{
"schedule_for": "ALTERNATE HOST USER ID" // can be userID or email
}
This will change the host of the meeting to the current alternate host.
Let me know if this works, or if I can provide any other help.