Skip to main content
DELETE
/
api
/
call
/
delete-batch
/
{batchId}
curl --location --request DELETE '{{baseUrl}}/api/call/delete-batch/6880bac05860c9b91c53c790' \
  --header 'Authorization: Bearer {{authToken}}'

{
  "success": true,
  "message": "Batch deleted"
}

​
Overview

Once you have exported or archived call outcomes, delete the batch to keep your workspace tidy and prevent accidental reactivation. Deleting is irreversible and removes the batch record from analytics views.

​
Prerequisites

  • Bearer token for an administrator.
  • Confirm no audits or dispute processes require the batch history.

​
Request

​
batchId
string
required
Identifier of the batch to delete.
​
Authorization
string
required
Bearer token authorised for Calling Management.
curl --location --request DELETE '{{baseUrl}}/api/call/delete-batch/6880bac05860c9b91c53c790' \
  --header 'Authorization: Bearer {{authToken}}'

​
Response

{
  "success": true,
  "message": "Batch deleted"
}
​
message
string
Confirms the deletion. Use it to log audit trails.

​
Error Handling

  • 400 Bad Request – Invalid batchId supplied.
  • 401 Unauthorized – Bearer token missing or expired.
  • 404 Not Found – Batch already deleted or does not belong to the workspace.
  • 500 Internal Server Error – Deletion failed; retry, then escalate with the batch id.
This operation cannot be undone. Export call data with GET /api/call/export/csv before removing the batch.

Authorizations

​
Authorization
string
header
required

Bearer token authentication for workspace access

Path Parameters

​
batchId
string
required

Response

Batch deleted