# 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/contacts/123' \
--header "Authorization: Bearer $POWERDIALER_API_KEY" \
--header "Idempotency-Key: $POWERDIALER_REQUEST_ID"{
"id": 123,
"deleted": true
}{
"error": {
"code": "invalid_api_key",
"message": "API key is invalid, expired or revoked",
"requestId": "00000000-0000-4000-8000-000000000004"
}
}Delete a contact
Delete the contact itself when your integration intends to remove that PowerDialer record. Requires contacts:write, and the contact must belong to the key’s workspace and permitted owner scope. Use its numeric PowerDialer ID; deleting by phone number is not supported here.
If you only want to take a lead out of one calling list, use the list-membership deletion endpoint instead. This endpoint is a contact deletion, not a membership-only change. It returns {id,deleted:true} when the operation succeeds; there is no request body.
Persist an Idempotency-Key before sending the delete. A matching retry returns the saved success even after the contact has been removed. A new logical delete of an already missing or inaccessible contact returns 404 not_found. 409 idempotency_conflict means the key was previously used for another request; do not discard your original operation record.
# 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/contacts/123' \
--header "Authorization: Bearer $POWERDIALER_API_KEY" \
--header "Idempotency-Key: $POWERDIALER_REQUEST_ID"{
"id": 123,
"deleted": true
}{
"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 PowerDialer contact ID, not your CRM externalId. The contact must be inside the credential’s workspace and owner scope.
1 <= x <= 2147483647