Vobiz Logo
Vobiz
|API Documentation
Console
← Back to Recording

Bulk Delete Recordings

Delete multiple recordings matching filter criteria (async operation).

This API allows you to delete multiple recordings at once based on filter criteria. This is an asynchronous operation that processes deletions in the background, making it efficient for removing large numbers of recordings.

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

  • • All recordings matching your filters will be permanently deleted
  • • Recording files will be completely removed from storage
  • • Recording URLs will no longer be accessible
  • • All metadata associated with these recordings will be deleted
  • • This operation cannot be reversed

🔄 Async Operation:

  1. Request is validated and queued as async task
  2. System identifies all recordings matching your filters
  3. Recordings are deleted in batches
  4. Operation typically completes within minutes to hours depending on volume

Best Practice: Before bulk deleting, use the List Recordings endpoint with the same filters to verify which recordings will be deleted. Check the meta.total_count to see how many recordings match.

HTTP Request

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

Authentication Headers

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

Query Parameters

Use query parameters to filter which recordings to delete. At least one filter parameter is recommended to avoid accidentally deleting all recordings.

Filter Parameters

NameTypeDescription
add_time__gte
stringDelete recordings created on or after this date. Format: YYYY-MM-DD HH:MM:SS. Example: 2025-01-01 00:00:00
add_time__lte
stringDelete recordings created on or before this date. Format: YYYY-MM-DD HH:MM:SS.
call_uuid
stringDelete recordings for a specific call UUID.
conference_name
stringDelete recordings for a specific conference name (supports partial match).
from_number
stringDelete recordings from a specific caller number (supports partial match).
to_number
stringDelete recordings to a specific destination number (supports partial match).
recording_format
stringDelete recordings with specific format. Values: "mp3", "wav".

Date Format Requirements:

  • • Format: YYYY-MM-DD HH:MM:SS
  • • Example: 2025-01-15 10:30:45
  • • Use 24-hour time format
  • • Include seconds (even if 00)
  • • URL encode spaces as %20

Response

Success Response (202 Accepted)

The bulk delete request has been queued and will be processed in the background:

Response - 202 Accepted
{
    "api_id": "correlation-id-uuid",
    "status": "successfully queued bulk delete request"
}

Note: A 202 response means the request has been accepted and queued. The actual deletion happens asynchronously in the background. Verify completion by checking if recordings still exist using the List Recordings endpoint.

Examples

Delete Recordings from January 2025

cURL
curl -X DELETE "https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/BulkDelete/?add_time__gte=2025-01-01%2000:00:00&add_time__lte=2025-01-31%2023:59:59" \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

Delete All Recordings for a Specific Conference

cURL
curl -X DELETE "https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/BulkDelete/?conference_name=TeamMeeting" \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

Delete Recordings from Specific Phone Number

cURL
curl -X DELETE "https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/BulkDelete/?from_number=%2B14155551234" \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

Note: URL encode the + symbol as %2B

Delete WAV Format Recordings

cURL
curl -X DELETE "https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/BulkDelete/?recording_format=wav" \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

Safe Workflow: Verify Before Deleting

Always check what will be deleted before running the bulk delete:

Two-Step Process
# Step 1: List recordings that match your filters
curl -X GET "https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/?add_time__gte=2025-01-01%2000:00:00&add_time__lte=2025-01-31%2023:59:59" \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

# Check the meta.total_count to see how many will be deleted

# Step 2: Review the output and confirm

# Step 3: Run bulk delete with same filters
curl -X DELETE "https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/BulkDelete/?add_time__gte=2025-01-01%2000:00:00&add_time__lte=2025-01-31%2023:59:59" \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

Combine Multiple Filters

Delete conference recordings in MP3 format from a specific date range:

cURL
curl -X DELETE "https://api.vobiz.ai/api/v1/Account/{Auth_ID}/Recording/BulkDelete/?conference_name=DailyStandup&recording_format=mp3&add_time__gte=2025-01-01%2000:00:00&add_time__lte=2025-01-15%2023:59:59" \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

Before Bulk Deleting - Checklist:

  • ✓ Use List Recordings endpoint first to verify count
  • ✓ Export/download recordings if you need backups
  • ✓ Double-check your filter parameters
  • ✓ Verify legal/compliance retention requirements
  • ✓ Confirm this is intentional (deletions are permanent)
  • ✓ Test with a small date range first if unsure

Common Use Cases:

  • • Clean up old recordings to reduce storage costs
  • • Delete test recordings from development/staging
  • • Remove recordings after exporting to external storage
  • • Comply with data retention policies (e.g., delete after 90 days)
  • • Remove recordings for specific conferences that ended

Tip: For automated cleanup policies, combine bulk delete with storage duration filters. For example, delete all recordings older than 90 days on a monthly schedule.

Verify Deletion:

After bulk delete completes, run the List Recordings endpoint with the same filters. If meta.total_count is 0, all matching recordings were successfully deleted.

Export Historical Recordings
Integrations