In my testing with the REST API I have found that updating the email attribute on an existing account appears to be impossible, triggering a 400 HTTP Response code and the following response:
"message": "Email already exists for: <user's name>"
If I send a blank value or the existing value via the Update Employee endpoint, the error code is avoided but the email attribute is not updated. Is this intentional? Users in our environment change emails infrequently, but it happens. Will I need to have the account deleted and re-added with a new email address to get around this? The documentation at https://docs.clover.com/reference#employeeupdateemployee-1 says nothing about the email address not being able to be updated. It also suggests that name is required to update an account, which I'm finding to not be true. This is the 3rd error I've found in the API documentation. Why are these not actively being fixed?