DocsICP FilingConsole
Documentation
Home Page ID Verification Information Verification Developer Reference Mobile number verification Detailed three-element mobile phone verification

Detailed mobile phone number three-element verification

Updated at:
Copy as MD
Product
My Favorites

This API performs a detailed 3-element verification. It checks that a provided mobile phone number is consistent with its corresponding name and ID number.

API information

Important

Before calling this API, read the integration process and activate the service.

  • API name: Mobile3MetaDetailVerify

  • Description: Verifies the authenticity and consistency of a provided mobile phone number, name, and ID number against an authoritative data source. If the information is inconsistent, the API returns the reason for the mismatch.

  • QPS limit: This API has a dedicated QPS limit. For more information, see QPS limits for identity verification APIs.

  • Service address (API endpoint):

    Region

    IPv4

    IPv6

    common

    cloudauth.aliyuncs.com

    cloudauth-dualstack.aliyuncs.com

    China (Beijing)

    cloudauth.cn-beijing.aliyuncs.com

    cloudauth-dualstack.cn-beijing.aliyuncs.com

    China (Shanghai)

    cloudauth.cn-shanghai.aliyuncs.com

    cloudauth-dualstack.cn-shanghai.aliyuncs.com

    Note

    • To reduce latency, select an endpoint that is geographically close to your servers.

    • You can also create a list of endpoints and poll them in rotation to improve availability.

    Important

    The Information Verification Service does not support a hard cap on call volume or automatic deactivation. To control costs and prevent high bills, configure spending alert rules after you integrate the service:

    1. Configure spending alerts: Set a spending alert rule (Set high-spending alerts) to monitor your bills in real time.

    2. Monitor data transfer plan balance: If you purchased a data transfer plan, also monitor its balance (Configure remaining quota alerts) to add resources or adjust your call policy promptly.

Request parameters

Parameter

Type

Required

Description

Example

ParamType

String

Yes

The encryption method. Valid values:

  • normal: The data is plaintext.

  • md5: The data is MD5 encrypted.

    Important

    • The ciphertext for all parameters must be a 32-bit lowercase MD5 string.

    • If an API call succeeds without encryption but fails with it, try using a different MD5 tool.

  • sm2: The data is encrypted by using SM2.

    Important

    For details on SM2 parameter encryption, see Parameter encryption reference.

normal

IdentifyNum

String

Yes

The ID number.

Note

Only ID numbers from Resident Identity Card and Residence Permit for Hong Kong, Macao, and Taiwan residents are supported.

  • If ParamType is set to normal, provide the ID number in plaintext.

  • If ParamType is set to md5, provide the ID number in ciphertext.

  • Plaintext: 429001********8211

  • Ciphertext:

    32fa7bcd874161bea8ec8fd98f390ec9

UserName

String

Yes

The name.

  • If ParamType is set to normal, provide the name in plaintext.

  • If ParamType is set to md5, provide the name in ciphertext.

  • Plaintext: Zhang San

  • Ciphertext:

    32fa7bcd874161bea8ec8fd98f390ec9

Mobile

String

Yes

The mobile phone number.

  • If ParamType is set to normal, provide the mobile phone number in plaintext.

  • If ParamType is set to md5, provide the mobile phone number in ciphertext.

  • Plaintext: 186****2055

  • Ciphertext:

    849169cd3b20621c1c78bd61a11a4fc2

Response parameters

Parameter

Type

Description

Example

RequestId

String

The request ID.

130A2C10-B9EE-4D84-88E3-5384FF039795

Message

String

The response message.

success

Code

String

The return code.

A value of 200 indicates a successful call. Other values indicate a failed call.

Important

  • This parameter indicates whether the API call was successful. For detailed descriptions of the return codes, refer to server-side error codes.

  • To see the business verification result, check the fields in ResultObject.

200

ResultObject

BizCode

String

The verification result:

  • 1: Consistent

  • 2: Inconsistent

  • 3: No record found

2

SubCode

String

The detailed verification result:

  • 101: Verification passed. The three elements are consistent.

  • 201: The mobile phone number is inconsistent with both the name and the ID number.

  • 202: The mobile phone number is consistent with the name but inconsistent with the ID number.

  • 203: The mobile phone number is inconsistent with the name but consistent with the ID number.

  • 204: Other inconsistencies.

  • 301: No record found.

201

IspName

String

The carrier:

  • CMCC: China Mobile

  • CUCC: China Unicom

  • CTCC: China Telecom

  • CBCC: China Broadnet

CMCC

SDK call examples

Important

Before you integrate, read the integration process, activate the service, and get an AccessKey and configure the environment variables.

Get SDK samples and installation packages:

  • On the online API debugging page in OpenAPI, find the SDK sample code on the right. Click SDK installation information in the upper-right corner of the code sample to view installation details.

    Note

    Select the required programming language.

    image

  • For offline installation, go to the SDK installation page, select the SDK for your programming language, and download it from the publishing address.

    image

Previous：Simplified 3-element verification for phone numberNext：Mobile number two-factor verification