Skip to main content
DELETE
/
api
/
v1
/
Account
/
{auth_id}
/
Recording
/
{recording_id}
Delete a recording
curl --request DELETE \
  --url https://api.vobiz.ai/api/v1/Account/{auth_id}/Recording/{recording_id}/ \
  --header 'X-Auth-ID: <api-key>' \
  --header 'X-Auth-Token: <api-key>'

Documentation Index

Fetch the complete documentation index at: https://docs.vobiz.ai/llms.txt

Use this file to discover all available pages before exploring further.

DELETE https://api.vobiz.ai/api/v1/Account/{auth_id}/Recording/{recording_id}/
Permanently delete a specific recording from your Vobiz account using its recording ID. Once deleted, the recording file is permanently removed and cannot be recovered.
Authentication required:
  • X-Auth-ID - Your account auth_id (e.g., {auth_id})
  • X-Auth-Token - Your account Auth Token
  • Content-Type: application/json
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.

​
Path parameters

FieldTypeRequiredDescription
auth_idstringYesYour account ID.
recording_idstringYesThe unique recording identifier to delete.

​
Response

​
Success Response (204 No Content)

On success, 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 does not 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

Retrieve recording details before deletion to confirm you are 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"
auth_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/${auth_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/${auth_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 is not an active or 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
To delete multiple recordings, use the Bulk Delete Recordings endpoint instead of making individual delete requests. This is more efficient and reduces API calls.
An HTTP 204 response indicates success. If you receive a 404 error and the recording ID is correct, the recording may have already been deleted by another process or user.

Authorizations

​
X-Auth-ID
string
header
required

Your Vobiz account Auth ID

​
X-Auth-Token
string
header
required

Your Vobiz account Auth Token

Path Parameters

​
auth_id
string
required

Your account Auth ID

Example:

"MA_XXXXXX"

​
recording_id
string
required

Response

204

Recording deleted