Deleting Calls
Deleting a call permanently removes all end-customer PII (transcript, recording metadata, contact details) associated with that call. This is distinct from cancelling a call, which only prevents a pending call from being dialled — deletion is a data-erasure operation on completed calls.
Deletion is permanent. Call transcripts, analytics, and contact information cannot be recovered after a delete operation.
- REST API
- Inbound Webhook
Using the REST API
Requires an API key with the calls:delete scope.
- Endpoint:
DELETE https://api.huskyvoice.ai/v1/calls/{call_id} - Auth header:
x-api-key: YOUR_API_KEY
- cURL
- Python
- JavaScript
- n8n
curl -s -X DELETE https://api.huskyvoice.ai/v1/calls/550e8400-e29b-41d4-a716-446655440000 \
-H "x-api-key: YOUR_API_KEY"
import requests
call_id = "550e8400-e29b-41d4-a716-446655440000"
url = f"https://api.huskyvoice.ai/v1/calls/{call_id}"
headers = {"x-api-key": "YOUR_API_KEY"}
response = requests.delete(url, headers=headers)
print(response.json())
# {"data": {"call_id": "550e8400-...", "deleted": true}}
const callId = "550e8400-e29b-41d4-a716-446655440000";
const res = await fetch(`https://api.huskyvoice.ai/v1/calls/${callId}`, {
method: "DELETE",
headers: { "x-api-key": "YOUR_API_KEY" }
});
const { data } = await res.json();
console.log(data.deleted); // true
Create an HTTP Header Auth credential in n8n: set Name to x-api-key and Value to YOUR_API_KEY. Select it in the HTTP Request node's Authentication field.
{
"name": "HuskyVoice – Delete Call",
"nodes": [
{
"parameters": {
"method": "DELETE",
"url": "https://api.huskyvoice.ai/v1/calls/550e8400-e29b-41d4-a716-446655440000",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth"
},
"id": "1",
"name": "Delete Call",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [250, 300]
}
],
"connections": {},
"settings": {},
"meta": { "instanceId": "huskyvoice-docs" }
}
Using Inbound Webhooks
Send a call.delete action to your webhook URL.
- cURL
- Python
- JavaScript
- n8n
curl -X POST https://api.huskyvoice.ai/v1/hooks/{YOUR_WEBHOOK_TOKEN} \
-H "Content-Type: application/json" \
-d '{
"action": "call.delete",
"data": {
"call_id": "550e8400-e29b-41d4-a716-446655440000"
}
}'
import requests
url = "https://api.huskyvoice.ai/v1/hooks/YOUR_WEBHOOK_TOKEN"
payload = {
"action": "call.delete",
"data": {"call_id": "550e8400-e29b-41d4-a716-446655440000"}
}
response = requests.post(url, json=payload)
print(response.json())
const response = await fetch(
"https://api.huskyvoice.ai/v1/hooks/YOUR_WEBHOOK_TOKEN",
{
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
action: "call.delete",
data: { call_id: "550e8400-e29b-41d4-a716-446655440000" }
})
}
);
const data = await response.json();
console.log(data);
Authentication uses the webhook token embedded in the URL. No separate credential setup is required in n8n.
{
"name": "HuskyVoice – Delete Call via Webhook",
"nodes": [
{
"parameters": {
"method": "POST",
"url": "https://api.huskyvoice.ai/v1/hooks/YOUR_WEBHOOK_TOKEN",
"sendBody": true,
"specifyBody": "json",
"jsonBody": "{\n \"action\": \"call.delete\",\n \"data\": {\n \"call_id\": \"550e8400-e29b-41d4-a716-446655440000\"\n }\n}"
},
"id": "1",
"name": "Delete Call",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [250, 300]
}
],
"connections": {},
"settings": {},
"meta": { "instanceId": "huskyvoice-docs" }
}
Payload schema:
| Field | Type | Required | Description |
|---|---|---|---|
action | string | Yes | Must be "call.delete" |
data.call_id | string | Yes | The call_id of the call to delete |
Response
200 OK
{
"data": {
"call_id": "550e8400-e29b-41d4-a716-446655440000",
"deleted": true
}
}
Error Responses
| Status | Code | Cause |
|---|---|---|
404 Not Found | NOT_FOUND | No completed call with that call_id exists for your organization |
401 Unauthorized | UNAUTHORIZED | Missing or invalid API key / webhook token |
500 Internal Server Error | INTERNAL_ERROR | Server-side failure |
Cancel vs Delete
| Cancel | Delete | |
|---|---|---|
| Works on | Pending / scheduled calls | Completed calls with recorded engagement |
| Effect | Prevents the call from being dialled | Permanently erases customer PII |
| Record kept? | Yes — status changes to cancelled | No — call data is removed |
| Reversible? | No (but data is preserved) | No |