We have a use case where a large number of meetings have already been created with scheduled hosts. It turns out that we really want one of the alternative hosts to be the Zoom host to free up the Meeting Host to facilitate. At this point we have two options:
Regenerate all the meetings, redistribute the links and update the contents of a table or
Use the update_meeting PATCH api to change the schedule_for to the new host
The issue I’m running into is that I am attempting to run an experiment updating these two fields:
Thanks for confirming @johnelrick. Can I kindly ask that you share the full request (including the actual emails of the host and alternative host) with us by opening a ticket here? This will help us to debug.
Before I enter a full ticket, except for the obfuscated emails that is my full request. I assumed the API would update only the fields passed in and leave the others intact. If that’s not the case, then I should attempt it with a full replacement (which will require additional coding to retrieve the full existing meeting information and then do a an update).
Is that how the process works? The documentation is a bit unclear as to what is required on an update call vs optional.
I do believe what you’re trying to do here should be possible—I see that you’ve already written in directly, and I’ve just replied back to you via email. I’ll continue the conversation there.
Getting same error while update meeting using PATCH method to change Existing host to New Host,
{“code”:3000,“message”:“You cannot schedule a meeting for .xx-user-id-xx.”}
If you are not allowing to change hosting for existing created meeting using field “schedule_for” field then why field schedule_for has been given for updation request ?
It very confusing that field is given to change host for existing meeting and its not working properly.
Getting same error while update meeting using PATCH method to change Existing host to New Host,
{“code”:3000,“message”:“You cannot schedule a meeting for .xx-user-id-xx.”}
If you are not allowing to change hosting for existing created meeting using field “schedule_for” field then why field schedule_for has been given for updation request ?
It very confusing that field is given to change host for existing meeting and its not working properly.
Its giving same error for licensed users and free users. Not working at all