it seems the start_url isn’t working as we have to sign in to zoom before the zoom app will launch.
We are getting the meeting data via the Api for our client’s website and populating a list of meetings with info and the start_url is the link to start the session.
Unless they are already signed in to zoom, clicking the start_url just takes them to zoom and asks them to sign in.
According to Zoom tech support, each start_url has a zak token which has a two-hour expiry on it. Once that 2 hours have elapsed, the user must log in. However, if they click a start_url that was generated less than 2 hours previously it should automatically sign them in and launch the zoom app.
So I have set myself a meeting, called it and populated the clients website via the API and then signed out of zoom and click the start_url of the meeting and it still asks me to log in, even though I have a start_url with a zak token that is less than two hours old?
We are also experiencing this problem. It seems to be related to the current issue, that join through the browser is in maintenance mode. Probably this was causing the same issue here, even though maintenance mode is a very recent problem.
Hi Tommy, thanks for the update. Unfortunately we moved on to use a different service because it was too risky for us to wait for an undefined amount of time. So we implemented another API.
We have experienced the same problems when trying to start the meeting with start_url. Currently we create the meeting in our API, we also get the zoom meeting, but when we start the class, we enter as attendees and not as hosts.