Still getting webhooks on deleted event subscription url on OAuth app

API and Webhooks
, ,
1

We have an OAuth app APP1 to receive webhooks on multiple environment endpoints for recordings and zoom phone events. I have deleted the event subscription url for staging environment on APP1 but still getting the web hooks on the staging url.

Since we are using another app APP2 for staging and checking the signature verification with secret token of APP2, all the web hooks coming from APP1 are rejected and 401 is sent back as response.

Questions:

  1. How can I stop the web hooks to staging url ?
  2. Is there any impact to the actual production app, if 401 is sent back from staging environment ?
2

To stop webhooks from being sent to a staging URL, you need to make changes to the configuration of the service or application that is responsible for handling the webhooks. The specific steps to stop webhooks from going to a staging URL may vary depending on the webhook provider and the setup you have in place. Here are some general steps you can follow:

  1. Access Webhook Configuration: Log in to the platform or service where you set up the webhooks. This could be a third-party service, an API, or a custom application you built.
  2. Locate Webhook Settings: Navigate to the settings or configuration section where you initially set up the webhooks. This is where you can modify the webhook endpoint URL.
  3. Update the Webhook URL: Look for the field that specifies the webhook endpoint URL. Replace the staging URL with the desired production or live URL where you want the webhooks to be sent.
  4. Save Changes: After updating the webhook URL, save the changes to apply the new configuration.
  5. Test Webhooks: Once you’ve updated the webhook URL, test the webhooks to ensure they are now being sent to the correct production URL and properly processed by your application or service.
  6. Monitor for Errors: After making changes, monitor the webhook traffic to ensure that there are no issues or errors with the new setup.
3

To stop webhooks from being sent to a staging URL, you need to make changes to the configuration of the service or application that is responsible for handling the webhooks. The specific steps to stop webhooks from going to a staging URL may vary depending on the webhook provider and the setup you have in place. Here are some general steps you can follow:

  1. Access Webhook Configuration: Log in to the platform or service where you set up the webhooks. This could be a third-party service, an API, or a custom application you built.
  2. Locate Webhook Settings: Navigate to the settings or configuration section where you initially set up the webhooks. This is where you can modify the webhook endpoint URL.
  3. Update the Webhook URL: Look for the field that specifies the webhook endpoint URL. Replace the staging URL with the desired production or live URL where you want the webhooks to be sent.
  4. Save Changes: After updating the webhook URL, save the changes to apply the new configuration.
  5. Test Webhooks: Once you’ve updated the webhook URL, test the webhooks to ensure they are now being sent to the correct production URL and properly processed by your application or service.
  6. Monitor for Errors: After making changes, monitor the webhook traffic to ensure that there are no issues or errors with the new setup.
4

Hi Tim,
That is exactly what I have done on feature page of Zoom Oauth APP1. I have removed the event subscription staging url but still getting web hooks on staging url.
The only thing that I didn’t do is to submit the app on the last page.