Permanently delete an end user and all associated data including recordings, transcriptions, and device bindings. This operation is irreversible and supports compliance requirements (e.g., GDPR right to deletion, HIPAA).
Authentication
Requires an API key with end_users:write scope.
curl -X DELETE https://api.bota.dev/v1/end-users/eu_abc123 \
-H "Authorization: Bearer sk_live_..."
Path Parameters
The end user’s unique identifier (e.g., eu_abc123).
Response
Returns 204 No Content on success.
What Gets Deleted
When you delete an end user, the following data is permanently removed:
| Resource | Action |
|---|
| End user record | Deleted |
| All recordings | Deleted (audio files and metadata) |
| All transcriptions | Deleted |
| All summaries | Deleted |
| Device bindings | Unbound (devices return to unbound status) |
This operation cannot be undone. All data associated with the end user is permanently deleted. Make sure to confirm with your user before proceeding.
Compliance Use Cases
GDPR Right to Erasure
When a user requests deletion under GDPR Article 17:
// Handle GDPR deletion request
async function handleDeletionRequest(customerUserId) {
// Look up the Bota end user ID from your mapping
const botaEndUserId = await getMapping(customerUserId);
// Delete from Bota
await fetch(`https://api.bota.dev/v1/end-users/${botaEndUserId}`, {
method: 'DELETE',
headers: { 'Authorization': 'Bearer sk_live_...' },
});
// Delete from your own system
await deleteFromYourDatabase(customerUserId);
// Remove the mapping
await removeMapping(customerUserId);
}
HIPAA Compliance
For healthcare applications, this endpoint supports patient data deletion requirements. Ensure you also maintain appropriate audit logs in your system. 
