| Excerpt |
|---|
Validates that the data complies with possible rules and performs the update if it does. Only the data provided in the payload is updated. The calling application must have permission to update accounts. When a "verified" data field is updated (for example, the mobile number for an SMS-verified account), a new verification will be triggered. The field will not be changed to the updated value until the verification is completed by calling endpoint 2004: Verify account |
| Endpoint ID: | 1003 | ||||||||||
| Method: |
| ||||||||||
| URL: | /user/dp-key/{dp-key}/data/{contract-id} /user/ext-key/{ext-key}/{ext-type}/data/{contract-id}
| ||||||||||
dp-key | dialogportal™ master key that uniquely identifies account to update | ||||||||||
| ext-key | External key that uniquely identifies account to update | ||||||||||
| ext-type | Type of external key | ||||||||||
| contract-id | Identifies the set of contract fields passed in the request body. If omitted, the default contract for the particular app is used. | ||||||||||
| Request body: | JSON data with properties corresponding to the fields in the specified contract. Only the fields included in the JSON payload is affected. Any omitted fields are left unchanged.
| ||||||||||
| None | ||||||||||
| Status codes: | 200 | Account was successfully updated with success | |||||||||
| 400 | Request is valid but data validation failed In case When the email address is configured to be unique, the following sub code may be returned:
In case When SMS verification is enabled, the following sub codes may be returned:
| ||||||||||
| 404 | Account was not found The following sub codes may be returned:
| ||||||||||
| 412 | App has no permission to update accounts | ||||||||||