When we use the zoom API for long time, the API meeting list does not include new meeting in the response. because of it teh code feels it is available at given time and try to scedule multiple meeting for same time slot
this issue will not come quickly. Since there are 44 accounts to get meeting for all acounts 10 mints will take, this is lot to load page, hence we are keeping all this meetings in cache, and we set ideal time-out and regular time interval for this application app pool to 0. so the cache will be there.
after 10-12 days of clearing the cache this issue will come. After clearing cache application will again work normally.
Rather then pinging the Zoom API every time before creating a meeting, I suggest a more efficient approach like using our Meeting Created, and Meeting Updated Webhooks to keep track of when the meetings are scheduled so you can avoid meeting time conflicts.
I suggest storing the meeting start_time and duration from the webhooks in your database, and then check your database, or update your frontend calendar to see if there are conflicts instead of hitting the Zoom API each time.
Hi Tommy,
we haev 44 zoom accounts,
We have created application, user can come to this application and select proper time of meeting and schedule. Application will call one by one account, and if any account is free at the given time. account will be scheduled.
we are checking if account is free and scheduling meeting using zoom API.
Can webhook do it?
@tommy I had a meeting with the customer today. The customer is asking how can he run a webhook with his 44 accounts. The customer is not familiar with how the webhooks function. Can you assist the customer in this aspect?
The Webhooks will tell you in real time if there is a meeting running for anyone on your Zoom account. The meeting is running if you have received a Meeting Started Webhook event, and not the respective Meeting Ended Webhook event.
to start meeting as a host we are appending zak to url. And in test environment API returning diffrenet zak which works fine and in production API returning different zak which is not correct, hence asking end user to continue as attendee.
why same API in diffreent environment getting different response.