Delete a Recording

Permanently delete a specific recording from your account.

This API allows you to permanently delete a recording from your Vobiz account using the recording ID. Once deleted, the recording file will be permanently removed and cannot be recovered.

⚠️ Warning: This action is permanent and cannot be undone!

• The recording file will be completely removed from storage
• The recording URL will no longer be accessible
• All metadata associated with this recording will be deleted
• This operation cannot be reversed

Best Practice: Before deleting, consider retrieving the recording details and downloading the audio file if you might need it for compliance or archival purposes.

HTTP Request

DELETEhttps://api.vobiz.ai/api/v1/Account/{auth_id}/Recording/{recording_id}/

Authentication Headers

X-Auth-ID:Your account auth_id (e.g., {Auth_ID})

X-Auth-Token:Your account auth token

Path Parameters:

• {auth_id} - Your account ID
• {recording_id} - The unique recording identifier to delete

Response

Success Response (204 No Content)

If the recording was successfully deleted, the API returns HTTP 204 with no response body.

Response - 204 No Content

HTTP/1.1 204 No Content

Error Response (404 Not Found)

If the recording doesn't exist or has already been deleted:

Response - 404 Not Found

{
    "api_id": "correlation-id-uuid",
    "error": "Recording not found"
}

Examples

Basic Delete Request

cURL

curl -X DELETE https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/abc123def456/ \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

Safe Delete Workflow: Verify Before Deleting

Best practice: Retrieve recording details before deletion to confirm you're deleting the correct file:

Two-Step Process

# Step 1: Get recording details to verify
curl -X GET https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/abc123def456/ \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

# Step 2: Review the output, confirm it's the right recording
# Check: call_uuid, conference_name, from_number, to_number, add_time

# Step 3: Delete if confirmed
curl -X DELETE https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/abc123def456/ \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

Archive Then Delete Workflow

Download the recording before deleting for backup purposes:

Bash Script

#!/bin/bash
RECORDING_ID="abc123def456"
ACCOUNT_ID="{Auth_ID}"
AUTH_ID="YOUR_AUTH_ID"
AUTH_TOKEN="YOUR_AUTH_TOKEN"

# Get recording details
RESPONSE=$(curl -s -X GET https://api.vobiz.ai/api/v1/Account/${ACCOUNT_ID}/Recording/${RECORDING_ID}/ \
  -H "X-Auth-ID: ${AUTH_ID}" \
  -H "X-Auth-Token: ${AUTH_TOKEN}")

# Extract recording URL
RECORDING_URL=$(echo ${RESPONSE} | jq -r '.recording_url')

# Download the recording file
echo "Downloading recording..."
curl -o "${RECORDING_ID}.mp3" "${RECORDING_URL}"

# Verify download was successful
if [ -f "${RECORDING_ID}.mp3" ]; then
  echo "Download successful. File size: $(ls -lh ${RECORDING_ID}.mp3 | awk '{print $5}')"

  # Delete from Vobiz
  echo "Deleting recording from Vobiz..."
  curl -X DELETE https://api.vobiz.ai/api/v1/Account/${ACCOUNT_ID}/Recording/${RECORDING_ID}/ \
    -H "X-Auth-ID: ${AUTH_ID}" \
    -H "X-Auth-Token: ${AUTH_TOKEN}"

  echo "Recording deleted successfully"
else
  echo "Download failed. Recording NOT deleted."
fi

Check Deletion Status

Verify the recording was deleted by attempting to retrieve it:

cURL

# This should return 404 if deletion was successful
curl -X GET https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/abc123def456/ \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

Before Deleting - Checklist:

✓ Download the recording file if you need to archive it
✓ Verify you have the correct recording_id
✓ Check for any compliance or legal requirements for retention
✓ Confirm this isn't an active/recent recording that might be needed
✓ Consider storage costs vs. retention needs

Common Use Cases:

• Remove old recordings to reduce storage costs
• Delete recordings after archiving to external storage
• Clean up test recordings from development
• Comply with data retention policies (e.g., GDPR right to deletion)
• Remove recordings that failed quality checks

Tip: For deleting multiple recordings, use the Bulk Delete Recordings endpoint instead of making individual delete requests. This is more efficient and reduces API calls.

Note: HTTP 204 response means success. If you receive a 404 error and you're certain the recording ID is correct, the recording may have already been deleted by another process or user.

List all Recordings

Export Historical Recordings