Confirming the download behavior of Phone Recording URLs returned by the Phone API

API and Webhooks
, ,
1

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

  • GET /phone/call_logs/{callLogId}/recordings → download_url
  • Webhook event: phone.recording_completed → download_url in payload

Description

We are building a pipeline that automatically downloads Zoom Phone recordings to external storage (Google Drive) upon receiving the phone.recording_completed webhook. The pipeline is working, but we would like to confirm three assumptions about the download_url behavior, as we could not find explicit documentation covering all of these points:

  1. Token expiration — The URL requires a valid access_token passed in the Authorization: Bearer header, and the token expires after the standard OAuth TTL (1 hour). After expiration, we must obtain a new token and re-request the recording. Is this correct?

  2. No persistent public URL — There is no API endpoint or Zoom interface that generates a persistent, publicly accessible sharing URL for Phone recordings (unlike Zoom Meeting cloud recordings, which have share_url). Is this correct?

Why this matters

If assumption 2 is correct, it means the only way to make a Phone recording accessible outside of Zoom is to download the binary file via the API and store it externally. We want to confirm this before committing to this architecture.

Any confirmation or correction would be greatly appreciated. Thank you!