HI @firstclass-support
Thanks for reaching out to us
I believe this is expected.
For users to be able to start a meeting, they should be logged in in their account
Hi @firstclass-support
Is it always the host of the meeting who is trying to start the meeting who is being asked to log in to their account?
I am not able to replicate this on my end, so can you please share with me meeting ID where you saw this behavior as well as the email of the host who was asked to log in before starting the meeting and another instance when this issue did not happen so I can take a look on my end
@firstclass-support , I would strongly encourage you to read up on the documentation regarding ZAK token.
You cannot remove the token expiration limit. You can however get the start meeting URL closer to the start of the meeting, so that the token is still valid for that span of time.
Create meeting just 2 hour ago before the meeting schedule.
Create a meeting way before hand. Get the host’s ZAK token, and append it to the start URL <2 hours before actual start time./
Example “https ://weshipcode.zoom.us/s/1231231234?zak=” + xxxxx.yyyyyy.zzzzz"
Create a meeting way before hand. Get the meeting details (using the Get a Meeting API ) <2 hours before the actual start time. This will give you the entire start URL https ://weshipcode.zoom.us/s/1231231234?zak=xxxxx.yyyyyy.zzzzz