Skip to main content
DELETE
This endpoint permanently deletes a cloned voice from both your organization’s database and the TTS provider’s system. This action cannot be undone.

Path Parameters

  • assistant_id (integer, required): The unique identifier of the assistant that owns the cloned voice.
  • voice_id (integer, required): The unique identifier of the cloned voice to delete.

Response

A successful deletion returns a confirmation message.
Response

Deletion Process

When you delete a cloned voice, the following actions occur:
  1. Provider Cleanup: The voice is deleted from the TTS provider (ElevenLabs, Resemble, etc.)
  2. Database Removal: All voice records and metadata are removed from the database
  3. Usage Logs: Historical usage logs are preserved for analytics
  4. Immediate Effect: The voice becomes unavailable for new synthesis requests
Permanent Action: Once deleted, a cloned voice cannot be recovered. You would need to re-upload the voice sample and recreate the cloned voice if needed.

Example Request

cURL

Error Responses

404 Not Found - Voice not found:
403 Forbidden - Insufficient permissions:
500 Internal Server Error - Provider deletion failed:

Integration Examples

Python - Safe Deletion with Confirmation
Node.js - Batch Deletion

Best Practices

Before Deletion

  1. Check Usage: Verify the voice isn’t actively used by assistants
  2. Backup Information: Save voice metadata and configuration if needed
  3. User Notification: Inform team members who might be using the voice
  4. Alternative Voices: Ensure alternative voices are available

Batch Operations

When deleting multiple voices:
  1. Rate Limiting: Add delays between deletions to avoid API limits
  2. Error Handling: Handle partial failures gracefully
  3. Logging: Keep detailed logs of deletion operations
  4. Rollback Plan: Have a plan to recreate accidentally deleted voices

Cleanup Strategy

Automated Cleanup Strategy

Recovery Considerations

Since deletion is permanent, consider these recovery strategies:
  1. Voice Sample Retention: Keep original voice samples to recreate voices if needed
  2. Metadata Backup: Export voice configurations before deletion
  3. Staging Environment: Test deletion procedures in a staging environment
  4. Alternative Providers: Have voices cloned with multiple providers as backup

Monitoring and Alerts

Set up monitoring for:
  • Voice deletion events
  • Failed deletion attempts
  • Accidental deletion of high-usage voices
  • Provider-side deletion failures

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

assistant_id
integer
required
voice_id
integer
required

Response

Successful Response