I am hitting a wall with the user provisioning API. The specific error is a 409 Conflict when trying to delete a user via DELETE /api/v2/users/{userId}. The response body says the user has associated interactions that prevent deletion.
I need to remove a user from the system because they left the company, but I can’t just delete them and lose the call history. The goal is to clean up the active user list without breaking the audit trail or the historical interaction data. I’ve tried deactivating them first with PATCH /api/v2/users/{userId} and setting enabled: false, but that doesn’t seem to clear the dependency for the delete endpoint.
Here is the code snippet I am using in my C# service:
var response = await client.Users.DeleteUserAsync(userId);
// Throws GenesysCloudApiException with status 409
The documentation for the Users API is a bit sparse on this specific constraint. It mentions that users can be deleted, but it doesn’t explicitly state that historical interactions block this. I checked the Interaction Search API, and the user ID is still referenced in the wrap-up-codes and interactions tables for calls made last year. If I delete the user, will those interactions become orphaned? Or is there a way to anonymize the user data before deletion?
I don’t want to write a custom script to scrub every interaction record manually. That seems like a bad idea for compliance. Is there a flag in the delete request I’m missing? Or do I need to use a different endpoint to ‘archive’ the user instead of deleting? The current approach feels wrong because the API is rejecting a valid request based on data that should be immutable. I’ve looked at the Terraform provider code, but it just calls the same API endpoints. Anyone have a workaround for this?