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.
| Endpoint ID: | 1003 | |||||||
| Method: | PUT | |||||||
| 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. Example 1 - Contract specifies full name and email. Password is not updateable according to contract: {
"name": "John Doe",
"email": "mailbox@mailserver.com"
}
| |||||||
Response body: | None | |||||||
| Status codes: | 204 | Account was updated with success | ||||||
| 400 | Request is valid but data validation failed In case the email address is configured to unique, the following sub code may be returned:
In case 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 | |||||||