I have been in contact with Instructure about our difficulties modifying a user's email address.  Our issue was the misuse of the skip_confirmation parameter.  The following does create an active ...

Hi Chris,The following:PUT https://myinstance.instructure.com/api/v1/users/:user_id?user[email]=newemail@institution.edu ...will create a new email address for the user and set it in the first...

Thanks for the response Marlee,Did you consider updating the user's email address using SIS imports, as you did when creating new users?

Thanks Scott, It appears that email changes must be made via the communication_channels api.  Do you have a sample call for modifying a user's email address? - Chris

Hooray!  The solution was found in our Canvas root account permissions.  Setting this option: Users can delete their institution-assigned email address Allowed us to do what we needed.  There are busi...

Hi Chris,The following:PUT https://myinstance.instructure.com/api/v1/users/:user_id?user[email]=newemail@institution.edu ...will create a new email address for the user and set it in the first...

I have been in contact with Instructure about our difficulties modifying a user's email address.  Our issue was the misuse of the skip_confirmation parameter.  The following does create an active ...

Thanks for the response Marlee,Did you consider updating the user's email address using SIS imports, as you did when creating new users?

Thanks Scott, It appears that email changes must be made via the communication_channels api.  Do you have a sample call for modifying a user's email address? - Chris

I am seeing similar behavior to what Marlee is reporting.  Email changes set by csv file are immediately active, whereas changes made by the API results in a communications_channel with a state of ...