Smile - updateTwoFaInfo API

2026-10-14 12:08

Overview

API URL: /api/v1/zoloz/smile/updateTwoFaInfo
API Description: Updates the phone number bound to a Smile user without unenrolling the user or re-capturing their face.
Note: This is a server-to-server API. No client SDK is required.

Request Parameters

Field Name	Data Type	Max Length	Required	Default Value	Description	Example
bizId	String	32	Yes	-	A unique business ID for tracing and idempotency purposes. For example, the sequence ID from the merchant's business-related database. Note: ZOLOZ does not validate the uniqueness of this value; the merchant side must ensure the uniqueness of the business ID.	"20260922000000000001"
userId	String	64	Yes	-	Merchant user ID, or other identifiers that can be used to identify a specific registered user. For example, mobile phone number, email address, etc. It is strongly recommended to pre-desensitize the value of the `userId` field; for example, by hashing the value.	"user_1234567890"
newTwoFaInfo	String	32	Yes	-	The new phone number. Must contain only digits and comply. Note: The old phone number (oldTwoFaInfo) is not required. The server queries the current value internally for comparison.	"8613800138000"

Response Parameters

Field Name	Data Type	Always Returned	Description	Example
result	Result	Yes	The API request result, which contains the result status, result code, and result message.	{ "resultStatus": "S", "resultCode": "SUCCESS", "resultMessage": "Success" }
transactionId	String	No	The unique transaction ID generated for this enrollment. Note: The system will only return the `<font style="color:rgb(38, 38, 38);">transactionId</font>` after the transaction enters the processing stage. If an error occurs before the transaction begins processing, the system will not return a `<font style="color:rgb(38, 38, 38);">transactionId</font>`. This includes, but is not limited to, the following situations: + Invalid request parameters, such as incorrect input format or missing required parameters. + The request fails to reach the server successfully, such as due to network issues or gateway failures. + The request is denied due to system rate limiting.	"G000000001FSE2025070100000001308203****"

Result

Common error codes

For the full list of common error codes, see the Common error codes section in the Error handling topic.

API-specific error codes

The following table shows the possible error codes that are specific for the Smile Verify Initialize API.

resultCode	resultStatus	Description
SUCCESS	S	Update succeeded.
SAME_TWO_FA_INFO	F	The new phone number is identical to the current one; no update is needed.

Sample

Request Sample

copy
{
    "bizId": "20260922000000000001",
    "userId": "user_1234567890",
    "newTwoFaInfo": "8613800138000"
}

Response Sample

copy
{
    "result": {
        "resultStatus": "S",
        "resultCode": "SUCCESS",
        "resultMessage": "Success"
    },
    "transactionId": "G000000001FSU20260922000000013082032459"
}