DELETE /api/v2/users/{id}
409 Conflict
{“errorCode”:“user_has_associated_interactions”,“message”:“User has associated interactions. Please remove or reassign them first.”}
I’m trying to script a bulk cleanup of terminated agents. The goal is to remove the user object while keeping their historical call data intact for compliance. The docs mention that deleting a user should just soft-delete them and leave the interaction data alone, but the API is throwing a 409 Conflict error every single time I hit an account with recent history. I’ve tried passing ?force=true and various headers, but the response is identical.
Here’s the curl command I’m running in a loop:
curl -X DELETE “https://api.mypurecloud.com/api/v2/users/{user_id}”
-H “Authorization: Bearer $TOKEN”
-H “Accept: application/json”
The error message suggests I need to “remove or reassign” interactions. That sounds like I have to manually go through every single call, chat, and email from the last 3 years and change the participant ID to “Unknown” or a generic “Legacy User” bucket. That’s insane. There has to be a way to just sever the link or flag the user as inactive without touching the interaction records. Is there a different endpoint? Maybe something in the `` or analytics API that handles this dissociation? Or am I missing a specific query parameter that allows force-deletion with data retention? I’ve checked the User Management API reference multiple times, and the DELETE endpoint description is just “Deletes a user.” It doesn’t mention the interaction dependency. I need a programmatic way to handle this because doing it manually for 500+ users is not an option. What’s the actual workflow here? Do I need to archive the interactions first via a different API call? Or is this a known bug in the v2 API?