...
Endpoint ID: | 1003 | |||||||||||
Method: |
| |||||||||||
URL: | /userentity/dp-keyid/{dpentity-keyid}/data/{contract-id} /userentity/ext-key/{ext-key}/{ext-type}/data/{contract-id}
| |||||||||||
dp-key | dialogportal™ master key entity-id | Rubiq entity ID that uniquely identifies an account to update | ||||||||||
ext-key | External key that uniquely identifies an 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 When verification is enabled, the following sub codes may be returned:
| ||||||||||
400 | Request is valid but data validation failed When the email address is configured to be unique, the following sub code may be returned:
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 |
...