# 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/contacts/123' \
--header "Authorization: Bearer $POWERDIALER_API_KEY" \
--header "Idempotency-Key: $POWERDIALER_REQUEST_ID"{
"listId": 456,
"contactId": 123,
"member": false
}{
"error": {
"code": "invalid_api_key",
"message": "API key is invalid, expired or revoked",
"requestId": "00000000-0000-4000-8000-000000000004"
}
}Remove a contact from a list
Remove a contact’s membership in one calling list while retaining the contact record. Requires lists:write and contacts:read. The credential must be allowed to access both resources; list access alone does not permit operating on an inaccessible contact.
Send the list and contact’s numeric PowerDialer IDs with no body. Success returns {listId,contactId,member:false}. The operation does not delete the contact or remove it from other lists. If you intend to delete the contact itself, use the separate contact deletion endpoint and review that action deliberately.
A persisted Idempotency-Key is required for safe recovery after a timeout. Matching retries return the saved result. 404 not_found means either the list or contact is missing or inaccessible; 400 invalid_request indicates invalid IDs. For 409 idempotency_conflict, restore the original operation 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/contacts/123' \
--header "Authorization: Bearer $POWERDIALER_API_KEY" \
--header "Idempotency-Key: $POWERDIALER_REQUEST_ID"{
"listId": 456,
"contactId": 123,
"member": false
}{
"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 <= 2147483647Numeric PowerDialer contact ID from a contact read/write or import result. The contact must be visible to this credential.
1 <= x <= 2147483647