DELETE /api/v2/users/9a8b7c6d-1234-5678-90ab-cdef12345678
Returns a clean 204 No Content. The flow continues right into the next routing block. Step one: we trigger the deletion from a Studio SNIPPET action after an agent offboards. Step two: the REST Proxy call finishes without errors, but the downstream analytics dashboard starts throwing 404 Not Found on any historical interaction tied to that ID. The transcript references break because the user object vanishes completely from the directory cache.
We’ve tried soft-deleting by passing a body to the request, but the endpoint just strips it out. Passing { “inactive”: true } inline with the SNIPPET assignment doesn’t change a thing. The SDK documentation hints at an archive parameter, but appending ?archive=true to the URL spits back a 400 Bad Request with {“code”:“bad_request”,“message”:“Unknown query parameter: archive”}.
The whole problem sits with the interaction history. When the user record gets wiped, all the past conversations lose their wrapUpCode and agent mapping in the analytics tables. We need a reliable way to detach the identity without nuking the reference pointers. Maybe there’s a specific header like X-NICE-DELETE-ARCHIVE: true or a separate provisioning endpoint that preserves the historical links?
The SNIPPET action just needs a working method to flag the account as removed while keeping the interaction metadata intact. Current workaround is a manual CSV export before deletion, which defeats the automation entirely. We’ve also tested the PATCH method with {“status”: “inactive”}, but that just locks the queue and leaves the record hanging in provisioning limbo. The REST Proxy logs show the request succeeds, yet the analytics pipeline still expects an active directory object to resolve the agent name.