Update phone — step 2: re-validate liveness (if required)
Update phone — step 2: re-validate liveness (if required)
Re-confirms the user with a live face capture when step 1 reports that liveness re-validation is needed. Returns a new data.phoneNumberOtpRequestId that replaces the one from step 1. Skip this call when liveness is not required. Step 2 of the update-phone-number flow. Not to be confused with the identically-named forgot-password endpoints.
Authentication
ApiKeystring
Static API key issued to your tenant. Required on every request.
OR
AuthorizationBearer
End-user JWT from registration or login. Required for verification, signing, and user-scoped operations.
Request
This endpoint expects an object.
phoneNumber
The new phone number, same value sent in step 1.
password
The user's current password.
image
Base64-encoded face image for the liveness check.
Response
data
error_code
error_message
error_descriptions