Skip to main content
Downloading a recording involves a multi-step process using the Vobiz API. Because recording files are stored securely, every request to access the physical file must be authenticated with your API credentials.

​
Step-by-step guide to downloading recordings

Follow these three steps to successfully list, retrieve, and download a recording file.

​
1. List all recordings

First, retrieve a list of available recordings to find the recording_id you need.
List Recordings
curl -X GET "https://api.vobiz.ai/api/v1/Account/{auth_id}/Recording/?limit=20" \
  -H "X-Auth-ID: {auth_id}" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN" \
  -H "Content-Type: application/json"

​
2. Retrieve Specific Recording Details

Once you have the ID, fetch its metadata to get the recording_url.
Get Recording Metadata
curl -X GET "https://api.vobiz.ai/api/v1/Account/{auth_id}/Recording/{recording_id}/" \
  -H "X-Auth-ID: {auth_id}" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN" \
  -H "Content-Type: application/json"

​
3. Download the physical file

Important: The download requires authentication. You must pass your X-Auth-ID and X-Auth-Token headers in the download request.
Always download using the exact recording_url returned by step 2 rather than hand-constructing a path. The host can vary (for example media.vobiz.ai, recordings.vobiz.ai, or storage.vobiz.ai) and the file extension matches the recording_format (.mp3 or .wav).
Download via cURL
RECORDING_URL=$(curl -s "https://api.vobiz.ai/api/v1/Account/{auth_id}/Recording/{recording_id}/" \
  -H "X-Auth-ID: {auth_id}" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN" \
  | jq -r '.recording_url')

curl -L "$RECORDING_URL" \
  -H "X-Auth-ID: {auth_id}" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN" \
  -o my_recording.mp3
Note: The -L flag ensures cURL follows any server redirects.

​
Common issues

SymptomCauseFix
401 UnauthorizedMissing or wrong X-Auth-ID / X-Auth-Token, or trying to open the URL in a plain <audio> tagSend both auth headers (see below).
404 Not FoundWrong recording_id, or the recording was deleted / expiredRe-list recordings and confirm the ID still exists.
Empty / truncated fileRedirect not followedAdd the -L flag so cURL follows redirects.
Wrong extensionSaved .wav for an MP3 (or vice versa)Match the file name to recording_format.

​
Why Dashboard Playback Fails

Dashboard playback may fail with a 401 Unauthorized error because standard HTML <audio> and <video> tags cannot send custom HTTP headers (like X-Auth-ID).

​
How to fix this on your platform

​
1. Server-side proxy

Create an endpoint on your own backend (e.g., /api/play?id=123) that fetches the file from Vobiz using your tokens and streams the binary data back to the dashboard.

​
2. Pre-download & serve

Use your server logic to download recordings to local storage first, and then serve them as static files directly to your clients.