# Add user profile

**POST /api/experience/profile**

Adds user profile data to the current experience interaction. <br/>- For `Register`: The profile data provided before the identification request will be used to create a new user account. <br/>- 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. <br/>- `ForgotPassword`: Not supported.


## Servers
- Logto endpoint address.: https://[tenant_id].logto.app (Logto endpoint address.)



## Parameters



## Body parameters
Content-type: application/json

- **type** ()
  The type of profile data to add. Available options: `email`, `phone`, `username`, `password`, `social`, or `extraProfile`.
- **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`.
- **values** ()
  The extra profile data to add. Only supported for `extraProfile` type. The data will be validated and split into standard user profile attributes and custom user profile attributes. The standard user profile attributes will be set to the user profile, whereas the custom user profile attributes will be set to the user custom data.
- **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. <br/> - `session.not_supported_for_forgot_password:` This API can not be used in the `ForgotPassword` interaction. <br/>- `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. <br/> - `session.identifier_not_found:` (`SignIn` interaction only) The current interaction is not identified yet. All profile data must be associated with a identified user. <br/>- `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. <br/>- The profile data is invalid or conflicts with existing user data. <br/>- The profile data is already in use by another user account. <br/>- The email address is enterprise SSO enabled, can only be linked through the SSO connector.


[Powered by Bump.sh](https://bump.sh)