Getting 400 Error While Creating Meeting Using API From Last Night
Simple Meeting Object Using JSON Request With Bearer Token
{
“topic”: “Test Meeting”,
“type”: 2,
“start_time”: “2020-12-21T08:30:00Z”,
“duration”: 55,
“timezone”: “Asia/Calcutta”,
“password”: “”
}
We have an admin account called classadmin@gla.ac.in and 98 sub accounts named as [classroom1@gla.ac.in], [classroom2@gla.ac.in] and so on.
Everything was working fine till 19th december and all APIs were working.
Since 20th december we are facing an issue described below
Using Master Account :
Access Token Generation : Working
API Call For Meeting Creation : Working
API Call For Other Task : Working
Using Sub Account :
Access Token Generation : Working
API Call For Meeting Creation : Not Working [(Returning Error Code -1, Status and NULL), Sometime It Returning 400 Bad Parameters With Same Data]
API Call For Other Task : Working
After This Thing We Have Come To Conclusion That Only Admin User Can Create Meeting Via API But No Sub Account Had This Privileges Which Was Working Fine Earlier.
Thank you for providing additional information. Just to clarify, you were/are using the Master Account Meeting APIs to accomplish this, is that correct?
We have to create around 1K classes per day which can not be possible to create using only admin user. We call meeting create API via same user in which account we want to create meeting.
Everything was fine just before 4-5 days but suddenly this is happing in our account all 98 licensed account are working under 99th admin account with single JWT App.
Even other APIs to get meeting data or usage reports are still working fine with same mechanism, only meeting create API returning 400, Code : -1, Status : NULL.
This API has a daily rate limit of 100 requests per day. Therefore, only 100 Create a Meeting API requests are permitted within a 24 hour window for a user.
I am in touch with Zoom Technical Team since 20 December .
After 4 days and more than 3 accelerations they have replied with 3 conversations and given time after 1 week.
Due to this, Our university classes getting disturbed very badly.
But let me hope they will give time soon.
Still not found any solution.
Checked everything.
Thank you for your patience. I brought this issue to two internal resources who are experts in this matter and they recommended that I reach out to our engineering team. I’ve since engaged our internal engineering team and will update you when I have more information as to why these requests are failing. (ZOOM-230959)
For the create Meeting API bug (error code 400 “-1” “null”) a workaround until we fix it is to pass the settings field and approval type in the API request. For example:
{
...
"settings": {
"approval_type":"{respective value here}"
}
}