# Update user profile data **POST /api/experience/profile** Adds user profile data to the current experience interaction.
- For `Register`: The profile data provided before the identification request will be used to create a new user account.
- For `SignIn` and `Register`: The profile data provided after the user is identified will be used to update the user's profile when the interaction is submitted.
- `ForgotPassword`: Not supported. ## Servers - Logto endpoint address.: https://[tenant_id].logto.app (Logto endpoint address.) ## Parameters ### Body: application/json (object) - **type** () The type of profile data to add. `email`, `phone`, `username`, `password`, etc. - **value** () The plain text value of the profile data. Only supported for profile data types that does not require verification, such as `username` and `password`. - **verificationId** () The ID of the verification record used to verify the profile data. Required for profile data types that require verification, such as `email`, `phone` and `social`. ## Responses ### 204 The profile data has been successfully added to the current experience interaction. ### 400 Invalid request.
- `session.not_supported_for_forgot_password:` This API can not be used in the `ForgotPassword` interaction.
- `session.verification_failed:` The verification record is not verified. ### 403 `SignIn` interaction only: MFA is enabled for the user but has not been verified. The user must verify the MFA before updating the profile data. ### 404 Entity not found.
- `session.identifier_not_found:` (`SignIn` interaction only) The current interaction is not identified yet. All profile data must be associated with a identified user.
- `session.verification_session_not_found:` The verification record is not found. ### 422 The user profile can not been processed, check error message for more details.
- The profile data is invalid or conflicts with existing user data.
- The profile data is already in use by another user account. [Powered by Bump.sh](https://bump.sh)