Webhook Endpoint Unresponsive

Hi, I have recently implemented the Server to Server OAuth API as the JWT one has deprecated. There’s a required webhook validation to be implemented as I needed the events to integrate with my application.

However, there have been 2 instances (Saturday 9pm) whereby I received an email from Zoom saying that my API endpoint is unresponsive.

I checked on my AWS logs and didn’t discover any issues or incoming requests. I went to the Zoom Platform and manually trigger the Validate and it shows the green word Validated.

So, I’m wondering why did it said that the endpoint is unresponsive?

Hi @ray.wong
Thanks for reaching out to us and welcome to our community, I am happy to help here!
When you received the email saying that your endpoint was unresponsive, were you still getting events in your endpoint? or did it also stop getting events?

Here is a link to our Docs about the Webhook URL revalidation

Hi Elisa, I stop getting events for at least 9 hours, before it worked again, without any change on my end. That’s what made me curious what happened.

Interesting @ray.wong
Can you please document this issue if it happens again and save some logs for me and share them with me please?

It seems like you’re experiencing an issue with Zoom’s Server to Server OAuth API and webhook validation. Here are some steps you can take to troubleshoot the problem:

  1. Check Webhook Configuration:
  • Double-check your webhook configuration in the Zoom Developer Dashboard. Ensure that the endpoint URL is correct and that it is set up to receive the necessary events.
  1. Review Server Logs:
  • Since you’ve checked your AWS logs and didn’t find any issues, it’s possible that the requests aren’t reaching your server. Verify that your server is properly configured to accept incoming requests.
  1. Logging in Your Application:
  • Implement detailed logging in your application to track incoming requests. This can help you identify if requests are reaching your server and if there are any issues with processing them.
  1. Error Handling:
  • Make sure your application handles errors properly. If there are any errors in processing the webhook payload, it’s important to respond with an appropriate HTTP status code and error message.
  1. Firewall and Security Groups:
  • Check your AWS security groups and firewall settings to ensure they are not blocking incoming requests from Zoom’s servers.
  1. Check for Rate Limiting:
  • Ensure that your server can handle the rate at which Zoom sends webhook events. If there are spikes in traffic, you may need to implement rate limiting on your end.
  1. Contact Zoom Support:
  • If the issue persists, consider reaching out to Zoom’s developer support. They may have specific insights or be able to provide additional troubleshooting steps.
  1. Monitor for Recurrence:
  • Keep an eye on your webhook endpoint to see if the issue recurs. If it happens again, try to capture any relevant logs or information that might help diagnose the problem.
  1. Network Latency:
  • Occasionally, there may be network latency issues that can cause requests to time out. Monitor your network performance to ensure it’s stable.

Remember to document any steps you take and the results you observe. This information can be helpful if you need to escalate the issue to Zoom’s support team.