Deleting Genesys Cloud user via API leaves orphaned interaction history

We’re cleaning up our tenant and need to remove a terminated agent’s account. The goal is to delete the user entity completely using the REST API, but we want to keep the historical interaction data (calls, chats) associated with that user intact for reporting purposes.

I tried the standard DELETE /api/v2/users/{userId} endpoint. The call returns a 204 No Content status, which means the user object is gone. The problem is that when I query the interaction analytics later, the data is either missing or attributed to a generic ‘Unknown’ user, breaking our audit trails. We need the user deleted from the active directory but the historical links preserved in the analytics database.

Here is the curl command I used:

curl -X DELETE "https://api.mypurecloud.com/api/v2/users/123456" \
 -H "Authorization: Bearer <token>" \
 -H "Content-Type: application/json"

I also tried deactivating the user first with a PATCH request to set enabled to false, then deleting. Same result. The user record disappears, and the historical data loses the reference.

Is there a specific flag or header to preserve the historical attribution? Or do we need to use a different endpoint? The documentation doesn’t mention a ‘soft delete’ or ‘archive’ option for users.

We’ve looked at the Bulk User API, but that seems to be for creation and updates, not deletion with retention. Any pointers on how to handle this without manual database exports? The current approach is too destructive for our compliance needs.