# Replace example resource IDs and ownerId with values from your workspace.
: "${POWERDIALER_API_KEY:?Set POWERDIALER_API_KEY to your scoped API key}"
# Set this once per operation; reuse it with the same request after a timeout.
: "${POWERDIALER_REQUEST_ID:?Set POWERDIALER_REQUEST_ID to a new UUID for this operation}"
curl --request DELETE \
--url 'https://api.migration.powerdialer.ai/api/public/v2/lists/456' \
--header "Authorization: Bearer $POWERDIALER_API_KEY" \
--header "Idempotency-Key: $POWERDIALER_REQUEST_ID"{
"id": 456,
"deleted": true
}{
"error": {
"code": "legacy_upload_delete_requires_app",
"message": "Lists with legacy uploads must be deleted in the PowerDialer app",
"requestId": "00000000-0000-4000-8000-000000000004"
}
}{
"error": {
"code": "invalid_api_key",
"message": "API key is invalid, expired or revoked",
"requestId": "00000000-0000-4000-8000-000000000004"
}
}Delete a calling list
Remove a calling list when the campaign or queue is no longer needed. Requires lists:write, and the credential must permit the list’s workspace and owner. Send the numeric list ID; no request body is required.
Lists linked to legacy uploads are refused with 409 legacy_upload_delete_requires_app; no records are deleted. Manage those uploads in the PowerDialer app. A list without linked uploads can be deleted while retaining its contact records. If you only want to unlink one contact, use membership deletion instead. Success returns {id,deleted:true}.
A persisted Idempotency-Key makes an uncertain delete recoverable: an identical retry returns the original success after deletion. A fresh delete of a missing or inaccessible list returns 404 not_found. A 409 idempotency_conflict means the operation key was reused for a different request.
# Replace example resource IDs and ownerId with values from your workspace.
: "${POWERDIALER_API_KEY:?Set POWERDIALER_API_KEY to your scoped API key}"
# Set this once per operation; reuse it with the same request after a timeout.
: "${POWERDIALER_REQUEST_ID:?Set POWERDIALER_REQUEST_ID to a new UUID for this operation}"
curl --request DELETE \
--url 'https://api.migration.powerdialer.ai/api/public/v2/lists/456' \
--header "Authorization: Bearer $POWERDIALER_API_KEY" \
--header "Idempotency-Key: $POWERDIALER_REQUEST_ID"{
"id": 456,
"deleted": true
}{
"error": {
"code": "legacy_upload_delete_requires_app",
"message": "Lists with legacy uploads must be deleted in the PowerDialer app",
"requestId": "00000000-0000-4000-8000-000000000004"
}
}{
"error": {
"code": "invalid_api_key",
"message": "API key is invalid, expired or revoked",
"requestId": "00000000-0000-4000-8000-000000000004"
}
}Authorizations
Issued in Developers. Workspace/owner/scopes come from credential, never acting-user headers. API keys cannot manage API credentials.
Headers
Persist one key for this logical operation before sending it. Reuse the same value only with the same method, path and body after a timeout. A changed request returns 409 idempotency_conflict; a matching retry returns the original response.
^[A-Za-z0-9._:-]{1,200}$Path Parameters
Numeric calling-list ID returned by POST /lists or GET /lists. The list must be visible to this credential.
1 <= x <= 2147483647