Webhook : phone.recording_completed: download_url itself returns 404 Not Found (Dev/Prod both receive the event)

API and Webhooks
, , ,
1

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

Description

We are receiving the phone.recording_completed webhook event in both Dev and Prod environments.

Details:

  • Same Zoom account (same organization)

  • Two separate Zoom OAuth apps:

    • Dev App

    • Prod App

  • Both receive the same webhook event for the same recording

When calling the /download_url itself, the HTTP response is 404 Not Found.

Observed behavior:

  • Sometimes Dev succeeds and Prod returns 404

  • Sometimes Prod succeeds and Dev returns 404

  • It never fails in both environments at the same time

This makes us suspect possible propagation delay, concurrency behavior, or app-context dependency.

We would like clarification on whether this behavior is expected.

Error?

The HTTP response is:

404 Not Found

This is not an authentication error (no 401 or 403).

The error occurs when calling the download_url directly.

How To Reproduce

1. Request URL / Headers / Body

Request URL:

GET https://api.zoom.us/phone/recording/download/{recording_id}

Headers:

Authorization: Bearer {access_token}

(No request body)

The download_url is taken directly from the phone.recording_completed webhook payload.

Questions

  1. After receiving a webhook event in the same Zoom account organization, are there any authentication or app-context restrictions when executing the provided download_url?

  2. Is there a recommended workaround or architectural pattern to avoid this issue?

We would appreciate clarification on whether this behavior is expected or if additional configuration is required.