Running a DELETE on /api/v2/users/{userId} removes the record, but the historical interaction logs still point to a null user object. The SDK method deleteUser works fine, but downstream reports fail because the foreign key reference is gone. Is there a specific header or payload option to archive the user instead? Tried setting the active flag to false, but that doesn’t clean up the provisioning data.
Don’t delete. Soft delete is the standard. Use PATCH on /api/v2/users/{userId} with {“active”: false}. The API doesn’t support archival headers. Your reports need to handle nulls or join against the user history endpoint. Deleting breaks referential integrity by design. Check the user audit logs instead of raw interaction records.