Zoom Webhook event logs unexpectedly displays a 500 response code

Hi there! Details using the template below, and can DM specific account / Zoom meeting details where required.

We have implemented the use of Zoom’s webhooks to monitor when cloud recordings have been completed.
We have had multiple instances whereby we’ve successfully received and a processed a webhook notification, but the Zoom Webhook logs indicated a 500 response code.

Multiple webhook notifications with a response code of 500 in Zoom’s Webhook logs, despite our webhook listener successfully processing the notification.

Which App Type (OAuth / Chatbot / JWT / Webhook)?

Which Endpoint/s?
I can DM our webhook end point if required.

How To Reproduce (If applicable)
Steps to reproduce the behavior:

  1. Launch a Zoom sessions and initiate cloud recording
  2. End the meeting
  3. Wait for the cloud recording to be processed and a Webhook notification to be sent
  4. Wait for the Listener to receive and process the webhook notification, and then check the Zoom Webhook logs.

Screenshots (If applicable)
N/A - I can direct message screenshots, UUIDs etc if required.

Additional context
Add any other context about the problem here.

Hi @ed.g,

Thanks for reaching out about this, and more than happy to look into this for you.

In order to make sure I can take a closer look, can I kindly ask you to send the following details to me at developersupport@zoom.us?

  • Example webhook payload you received successfully that shows 500 error in the logs, and timestamp
  • The endpoint URL you’re receiving Zoom payloads at
  • Example Meeting ID or UUID
  • If possible, a screenshot of the associated 500 error in the logs

Thanks, and I’ll keep an eye out!


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.