Error codes

Error code

Description

Cause and suggestion

600000

A success code is returned.

-

600004

The solution ID does not exist.

Confirm that you have created a solution ID in the Phone Number Verification Service console.

600010

An unknown exception occurred.

Possible causes:

• The JwtToken is invalid.

• A syntax error exists in the success callback.

• A network exception occurred.

600011

Failed to obtain the token.

Possible causes:

• The Wi-Fi switch was enabled during number acquisition.

• Browser settings, such as data-saving mode or network settings. For more information, see FAQ.

• Other causes. For more information, see Carrier error codes.

600013

The feature is unavailable due to carrier maintenance or upgrade.

Switch to another logon method and try again.

600014

The number of calls for this feature has reached the upper limit because of carrier maintenance or an upgrade.

Switch to another logon method and try again.

600015

API call timed out.

Try to log on using only the cellular network. You can also toggle airplane mode on and off, and then reopen the authorization page to check if the issue is resolved.

600018

The phone number is restricted by the carrier.

Contact the carrier to resolve this issue.

600025

The identity verification of the accessor failed.

Check whether a solution ID was created successfully.

600028

Invalid input parameters (accessToken or jwtToken).

Check whether the accessToken and jwtToken parameters are empty.

600030

Non-compliant CSS properties.

The title, protocol, and button cannot be empty. Check whether the related CSS properties are empty.

600032

Invalid business type.

This error code is returned in versions 2.1.6 and later. Check whether the BizType input parameter for the server-side GetAuthToken API is passed correctly.

600034

The request parameters have expired.

Call the server-side GetAuthToken API again to obtain a new authorization token.

Error code

Description

Recommended action

600000

The token is successfully obtained.

-

600001

The authorization page is displayed.

-

600002

Failed to display the authorization page.

Reset the network. You can toggle airplane mode on and then off. You can also switch to another logon method, such as text message or WeChat.

600004

Failed to obtain carrier configuration information.

Upgrade the SDK to the latest version. You can download the latest SDK from the Phone Number Verification Service console.

600005

The mobile device is insecure. For information about possible causes, see Causes of the '600005: The mobile device is insecure' error.

Switch to another logon method, such as text message or WeChat.

600007

No SIM card is detected.

Check the SIM card and retry.

600008

The cellular data network is not enabled.

Enable the cellular data network and retry.

600009

The carrier cannot be identified.

Make sure that the carrier is China Mobile, China Unicom, or China Telecom. Other carriers are not supported.

600010

An unknown error occurred.

Check whether the SIM card is working as expected. For example, check whether the payment for the SIM card is overdue. You can also restart the cellular network and retry.

600011

Failed to obtain the token.

Check whether the SIM card is working as expected. For example, check whether the payment for the SIM card is overdue. You can also restart the cellular network, restart the mobile phone, or switch to another logon method.

600012

The number could not be pre-fetched.

Check the cellular data network and retry. You can also toggle airplane mode, restart the mobile phone, or switch to another logon method.

600013

The feature is unavailable because the carrier is performing maintenance or an upgrade.

Switch to another logon method.

600014

The call volume for this feature has reached the upper limit because the carrier is performing maintenance or an upgrade.

Switch to another logon method.

600015

The API call timed out.

Try to log on using only cellular data. You can also toggle airplane mode on and off and then display the authorization page again to check whether the issue is resolved.

600017

Failed to parse the package name, package signature, BundleID, or AppID of the client app, or the solution key does not match your app information.

Make sure that the app information in your project matches the key details of the solution in the Phone Number Verification Service console. We recommend that you perform the following checks:

• For Android, check whether the app signature has changed, or whether the solution key generated based on the app information is correctly synchronized to the code.

• For iOS, make sure that the BundleID of the app matches the key and that the correct key information is synchronized to the code.

600021

The carrier was switched when the user tapped Log on.

Switch to another logon method, such as text message or WeChat.

600023

An error occurred when loading custom controls.

Check whether the custom controls are added correctly.

600024

The device environment is ready for authentication.

-

600025

Invalid device check parameters.

Check whether the type and range of the input parameters are valid.

600026

The acceleration or pre-authentication API cannot be called after the authorization page is loaded.

Check whether the preLogin or accelerateAuthPage API is called after the authorization page is displayed. This behavior is not allowed.

Error code

Error Code Descriptions

130010

A parameter is empty.

105112

The timestamp is invalid.

103101

The request signature is invalid.

110024

The BusinessType is misconfigured.

110025

The BusinessType is invalid.

110023

The application does not have the required access permissions.

110025

The access permissions have expired.

103111

The WAP gateway IP address is invalid.

111002

The user's number is blacklisted.

103609

IoT IP addresses are not allowed to get phone numbers.

105002

Failed to get the phone number from the China Mobile gateway.

105312

Insufficient capacity.

• For a newly created solution ID, you must wait 15 to 30 minutes for the service to be synchronized on the China Mobile side. This error is reported if the service is not synchronized.

• This error is reported if the payment for the mobile phone number is overdue.

103211

Other errors.

170001

• Referer validation failed. A common cause is that the Referer is empty because of a cross-domain HTTPS request. If you use HTTPS for access in a production environment, add the required code to the head.

• The Referer URL of the integrated page is different from the one registered on the open platform. Register the correct URL for the integrated page.

• Origin validation failed. A common cause is that the request source registered on the open platform is different from the actual source. For example, the origin ends with a forward slash (/). For more information, see the origin description.

111002

The phone number is not passed through the gateway.

Common cause: The service uses the cellular data network of China Unicom or China Telecom, or a Wi-Fi network.

110027

The service is unavailable.

Common causes: The contract is not attached or the contract balance is insufficient. The configuration requested on the platform has not taken effect.

130016

Failed to decode.

Common cause: The public and private keys of the user are not generated using the specified utility class method.

• The registered public key of the user does not match the private key

• The signature is not generated using the specified utility class method

• An error occurred when encrypting the phoneNum

130018

Signature verification failed.

Common cause: The public and private keys of the user are not generated using the specified utility class method.

• The registered public key of the user does not match the private key

• The signature is not generated using the specified utility class method

• An error occurred when encrypting the phoneNum

130032

Parameter parsing error.

Common cause: The message format is invalid. It is not in the standard JSON format.

103605

The encryption method or key value is empty.

Common cause: The service that is being debugged on the production network accesses the address of the staging environment by mistake, or the platform configuration has not taken effect.

110025

The access permissions have expired. Check whether the service has expired on the service configuration page.

120020

Token validation failed.

Common causes:

• The token has expired

• The userinformation is missing or an encoding error occurred

• The token is repeatedly validated

121011

The number of verification attempts for the phone number has reached the limit. By default, a mobile phone number can be verified up to 10 times per day.

999999

A system exception occurred.

Common causes: Network fluctuations or an error occurred when encrypting the phoneNum during token validation.

Error code

Description

Recommended action

100

Success.

-

1101

Invalid public IP address.

The access request is not from valid data traffic. Check the public IP address.

1102

Invalid private IP address.

Information cannot be obtained using the private IP address. Restart the phone and try again.

1105

Invalid parameter information.

The SDK request parameters are abnormal.

1106

The application key information does not match.

The application parameter settings are abnormal.

1107

Insufficient balance.

Contact China Unicom for feedback.

1201

Failed to retrieve the number.

The SDK API request failed. Try again.

1203

Failed to obtain the authorization code.

Internal service query failed. Try again.

2101

Authentication failed.

SDK identity verification failed.

2201

Invalid APP ID.

The APP ID is inactive or invalid.

2202

Invalid application information.

The application information does not match the registered information.

2203

Invalid SDK information.

SDK information verification failed.

2205

Access information parsing error.

Failed to parse user information.

2206

The request throttling limit is exceeded.

The number of access requests exceeds the throttling limit.

3201

The system is busy.

An internal service exception occurred.

3202

Internal gateway error.

-

3203

Internal routing error.

-

3204

No payment permission.

-

3205

The number service is unavailable in this province.

-

3206

The ticket issuance feature is temporarily unavailable.

-

3207

This feature is not supported.

-

10100

No network connectivity.

The device is not connected to a network, or the current network connection is poor and unstable.

10101

The device is not connected to a cellular network.

The cellular network is not enabled on the device.

10102

The ApiKey cannot be empty.

A parameter passed to the initialization method is empty.

10103

Timeout.

The SDK API call timed out.

10106

A data decryption exception occurred.

The SDK failed to decrypt the data.

10109

General error.

A general or unknown error occurred.

20101

A maximum of 50 authorization codes can be obtained within 10 minutes.

The SDK performs local real-time request throttling.

30200

Invalid server-side data format.

The SDK cannot parse the API response.

-2

Invalid server-side data format.

The access request is not from valid data traffic.

410000

Request timed out.

Mobile networks are complex. A timeout error can occur if the timeout period is too short.

To prevent timeout errors, we recommend that you set a timeout period.

We recommend that you set the timeout period to more than 3 seconds.

410001

Failed to obtain the token.

Call the pre-fetch API first.

410002

An exception occurred when parsing the service response.

The data returned by the phone number retrieval service cannot be parsed.

410003

Failed to switch to the cellular network.

When both Wi-Fi and the cellular network are enabled,

You cannot force phone number retrieval requests to use the cellular data network.

Output.

410004

The cellular network is not enabled.

The cellular network is detected as disabled.

410005

A network detection exception occurred.

During the network provisioning check and the switching procedure

The exception that was caught.

410007

Pre-fetched number has expired.

-

410010

The HTTP status code is 200 or 302.

any other values.

-

410011

An exception was thrown during HTTPS communication.

-

410012

The status code is 200, but the response body is empty.

-

410013

Invalid redirect address.

-

410021

Initialization failed or operations are too frequent.

-

410024

An exception was thrown during HTTP communication.

-

Error code

Error code descriptions

30002

The user's network cannot be identified. Two redirection addresses for getting phone numbers from other carriers are returned.

30901

Failed to exchange the code for a token. The code has been used or has not been used for more than 10 minutes.

-64

No permission. The e-Surfing account platform has not granted the application the required access permissions.

-20005

The signature is invalid.

-10001

Could not obtain a number.

-10002

A parameter is invalid.

-10003

Decryption failed.

-10004

The IP address is invalid.

-10005

An exception occurred in the callback parameters for cross-carrier authorization.

-10006

Authorization failed on the China Telecom network.

-10007

Redirected to another carrier to get the phone number.

-10008

The preset threshold for getting phone numbers is exceeded.

-10009

The timestamp has expired.

-20005

The signature is invalid.

-20006

The application does not exist.

-20007

The public key data does not exist.

-20100

Internal parsing error.

-20102

Failed to parse the encrypted parameters.

-30001

The timestamp is invalid.

51002

A parameter is empty.

51114

Cannot get the mobile phone number data.