Account Update
4 min
\<font color="#b6c7cb">\</font> topic type concept purpose account update event overview and guidance on when to send the event audience developers implementing account profile or settings changes applies to integrations evaluating changes to existing account details does not apply to account creation or authentication events call accountupdate when a user attempts to update the address, payment method, password, or other account information post authentication on your website timing the api call should come to the after a user attempts to update an account after they pass error handling and you retrieve their ip address and user agent before you update the account important considerations when calling accountupdate we recommend you send all values associated with the account even if they are not being updated previousvalues send all values from before the update updatedvalues send all values from after the update (changed or unchanged) emailaddress is an important field and should always be present with the value post update this means, if your site does not allow email updates, the same email address will be passed 3 times in the emailaddress field, the previousvalues block, and the updatedvalues block we suggest you call the accountupdate event even if something we don't collect is changed \<font color="#4f6228">example\</font> some clients have preferences such as a user's avatar or preferred rental car type flow account update flow diagram user logs in user goes to account update and changes something (address, payment methods, personal info) client processes frontend validation to ensure all fields are filled in properly send changes to backend client's backend server calls accertify with all previousvalues (before the change) and updatedvalues (after change) regardless if they changed or not see also account update fields https //atlas accertify com/public apis/account update fields