When we try to set up/edit a Zoom event through our LMS via the API, we get an error message:
{“code”:403,“message”:“Access to the Zoom REST API has been denied for this user. Contact Zoom Support for details.”}
We use the Zoom API on our LMS to create Zoom webinars and meetings. We create these events in the LMS, which uses the API to create them in Zoom. Part of this integration also sends Zoom registration emails to those who enroll in our events.
We receive this error when we attempt to save the event in the LMS, which creates the event in Zoom via the API. This error also occurs when a student tries to join an already-existing event that has already started using this same module, which gives them a button to directly join the Zoom conference in progress.
We’ve never seen these errors before. And we’re not attempting to do anything that we haven’t been doing for years already.
Hi @Maribeth
welcome to the community.
403 is a general error.
What LMS is this?
Have they setup the connection or are you?
Do you have a registration in the marketplace where you get your client secret?
What method are you using I asuume server-server?
Have you setup an app in the marketplace for developer (your account only) use?
How are you connecting to the server and are you using OAUth to get your “keys”
The security of Zoom has progressed over time and it could be the way you use is now out of date.
Thank you for your response. Unfortunately, I don’t know what some of your questions mean. I have forwarded this on to the person reporting the trouble. I have attached a copy of their email response with a screenshot, that may or may not help. It’s like finding a needle in a haystack.
Thank you so much for your support/suggestions.
-Maribeth
(Attachment zoom_api_issue_email_from_colton_07282025.pdf is missing)
I was not able to include any attachment or add any screenshots to my last response. If you are allowed, you can reach out to me directly at mchapman@ala.org and I can share them with you.
Hi @Maribeth
Thanks for sharing those details with us and thanks to John for starting this conversation!
I will send you a DM so you can share that email with me.
Thank you so much for your response, Elisa. We believe we have successfully addressed the issue, and all seems to be working now. Had to do with an app being owned by a former staff member. Also having to do with server-to-server and OAuth. Way over my head, but I have colleagues that were able to address the situation…finally! Was just such a mystery!
Thank you so much for your response, and offering assistance, John. We believe we have successfully addressed the issue, and all seems to be working now. Had to do with an app being owned by a former staff member. Also having to do with server-to-server and OAuth. Way over my head, but I have colleagues that were able to address the situation…finally! Was just such a mystery! I truly appreciate your even responding to my post.