| Excerpt |
|---|
Activates an entity/account in case , when the contract specifies that all new accounts are created inactive until activated by the userentities must be verified before they can be used. This endpoint is also used to complete entity updates which require verification, such as updating a mobile number for an SMS-verified entity. |
| Endpoint ID: | 2004 | |||||||
| Method: |
| |||||||
| URL: | /userentity/dp-keyid/{dpentity-keyid}/verify /userentity/ext-key/{ext-key}/{ext-type}/verify
| |||||||
| dp-key | dialogportal™ master key entity-id | Rubiq entity ID that uniquely identifies an account to verify | ||||||
| ext-key | External key that uniquely identifies an account to verify | |||||||
| ext-type | Type of external key | |||||||
| Request body: | Optional JSON data with code for verification.
| |||||||
| None | |||||||
| Status codes: | 204 | Account The entity was verified with successsuccessfully verified | ||||||
| 400 | Request is valid but data validation failed The following sub codes may be returned:
| |||||||
| 403 | Verification code doesn’t match the code stored in the database | |||||||
| 404 | The entity was not found The following sub codes may be returned:
| |||||||
| 501 | Account The entity can not be verified, either because the account entity does not require verification or because verification has already been carried outperformed. The following sub codes may be returned:
| |||||||