Webhooks not delivered for OAuth-connected accounts for our Published zoom App

API Endpoint(s) and/or Zoom API Event(s)

  • Webhook Endpoint: (One app sends three webhook notification, across our clusters)

    • POST https://zoom-cluster1.testpress.in/zoom-webhook/
    • POST https://zoom-cluster2.testpress.in/zoom-webhook/
    • POST https://zoom-cluster3.testpress.in/zoom-webhook/
  • Events expected:

    • meeting.started
    • meeting.ended
    • recording.completed

OAuth App Type:

  • Published - Zoom Marketplace OAuth App (single app used across multiple tenants/clusters)

Description
We are integrating Zoom using a single OAuth Marketplace app across multiple clusters in our LMS platform. And our app was verified and published by Zoom App reviewer team months ago.

Now the issue is that webhook delivery is inconsistent across different Zoom customer accounts:

  • For some Zoom accounts (internal/test accounts), webhook events are received correctly.
  • For clients Zoom accounts, no webhook events are delivered at all, even though OAuth installation succeeds and meetings are created normally.
  • The same app, same webhook URL, and same backend infrastructure is used across all accounts.

We have verified that:

  • OAuth flow completes successfully for all accounts
  • Meetings are created and triggered normally in Zoom
  • Our server logs (nginx/application logs) show no incoming requests at all for affected accounts
  • No application-side errors (Sentry/logging) are observed
  • We checked the client account and noticed that the webhooks were there in the “Event logs” section of our app which the client connected.

Error?
No explicit error is returned. Webhook is not received to the webhook endpoints.

How To Reproduce
Steps to reproduce the behavior:
The steps to reproduce requires access to our SaaS application and would be happy to provide the details and access to our testing platform via PM.

@Testpress1 regenerate your authorization url for the new webhook url to take effect.

Currently there are 404 errors as they are still trying to reach the old endpoints