On Mon, 16 Sep 2019 15:40:10 GMT, I issued a DELETE request to "https://api.zoom.us/v2/meetings/414861164?" and got a 500 response without a body. However, the meeting was indeed deleted.
If I try a DELETE on a nonexistent meeting, I get a proper 404.
Just wondering why the 500 response.
tommy
(Tommy Gaessler)
September 16, 2019, 5:01pm
2
Hey @ron.straight ,
The 500 does seem odd. I tried to reproduce the error and I could not.
Are you including any query parameters ?
Thanks,
Tommy
No query parameters.
I didn’t notice the 500 response from DELETE requests until around the time I toggled the app intent to publish and got my developer credentials.
tommy
(Tommy Gaessler)
September 16, 2019, 6:01pm
4
Hey @ron.straight , is the 500 error still happening? Or did it just happen that once ^
@tommy Yes, it’s still happening consistently. Just tried it a minute ago.
tommy
(Tommy Gaessler)
September 16, 2019, 6:37pm
6
Thanks @ron.straight ,
Can you give me exact steps to reproduce?
What app type? (Account/User Level OAuth or JWT)
What type of meeting? (Recurring, scheduled, instant)
When are you deleting it? (Before, During, or After meeting has started)
Thanks,
Tommy
tommy
(Tommy Gaessler)
September 16, 2019, 7:50pm
8
Thank you @ron.straight .
This may be due to your account being a Basic account.
To use the Zoom APIs you need at least a Pro account . Or you can request a Free Trail account to use/test the Zoom APIs.
Let me know how you want to move forward.
Thanks,
Tommy
You mention a trial account, but I assume that’s only for testing, right? If we actually want to create an app that other users can use, it has to be owned by at least a Pro account?
tommy
(Tommy Gaessler)
September 16, 2019, 8:53pm
10
A free trail account can create and publish apps to the Marketplace for as long as the free trail period.
If you want your App to work long term yes, I would suggest upgrading to the Pro Account .
Does that make sense?
Thanks,
Tommy
I wouldn’t say it makes sense, but I understand what you’re saying.
It will at least be easier to test OAuth with users under our account.
Thanks!
tommy
(Tommy Gaessler)
September 16, 2019, 9:46pm
12
@ron.straight , you can reach out to isv@zoom.us to request a free trail account to test / develop your application.
Thanks,
Tommy
@tommy Still getting that 500 when performing a DELETE on a meeting after upgrading to a Pro account. The deletion happens, but the response indicates otherwise.
tommy
(Tommy Gaessler)
September 19, 2019, 10:38pm
14
Thanks @ron.straight ,
This does seem like a bug. Can you give me a few of your meeting ID’s where you saw the 500 error so I can look at the logs?
Thanks,
Tommy
Hey, @tommy .
I just deleted 226213781 and 370927595 a few minutes ago.
1 Like
tommy
(Tommy Gaessler)
September 20, 2019, 10:08pm
16
Thanks @ron.straight !
We will look at the logs and see what’s going on.
Will post back here with updates. ZOOM-110814
Thanks,
Tommy
tommy
(Tommy Gaessler)
September 24, 2019, 10:27pm
19
Update, this may be related to moving a Personal Zoom Account to a Sub Account under a Master Account.
See:
Update, this is an edge case on our end where you create a Zoom App on the Marketplace on a Personal Zoom Account, then your Zoom Account is added to a Master Account as a Sub Account. The Apps in the App Marketplace aren’t transferred over to the Master Account properly.
As a work around, create a new Zoom Marketplace App and it will be properly instantiated on the Master Account.
We are working on fixing this. JIRA: ZOOM-111363
Thanks,
Tommy
We are looking into this edge case and will fix.
Thanks,
Tommy
@tommy , after recreating the app, I’m still getting 500 on DELETE. Same behavior as before. The meeting is deleted, but the response has a status 500.
Just deleted 931674664 and 964129786.
tommy
(Tommy Gaessler)
September 26, 2019, 10:57pm
21
Thanks for the update @ron.straight
Can you send me a screenshot of your App’s request logs in the Zoom App Marketplace Dashboard after you get the 500 error?
https://marketplace.zoom.us/user/logs
Thanks,
Tommy
I didn’t know about that page. Very useful!
As you can see, it says it returned a 204. That makes me wonder if maybe the error is from our proxy. I don’t even see the DELETE calls in our logs, and checking the code shows we may not be handling an empty response body correctly.
I’ll let you know if I find anything contrary, but for now I think we can assume this is on our end.
Sorry for wasting your time. I’ll know to check the API logs next time before I go crying wolf.
1 Like