All Products
Search
Document Center

ID Verification:MOBILE_2META

Last Updated:Oct 23, 2026

This topic describes the MOBILE_2META API.

API description

  • API operation name: Mobile2MetaVerifyIntl

  • Request methods: POST and GET

  • Protocol: HTTPS

  • Description: Verifies that a name and mobile number match records from an authoritative data source.

  • QPS limit: Each API has its own QPS limit. For more information, see QPS limits of ID Verification server-side APIs.

  • Service endpoints:

    Note
    • Benefits of internal network access: An internal network is a private communication network connecting Alibaba Cloud products within the same region. If your application server is deployed in the same region, use the internal endpoint to access the ID Verification service for enhanced security and stability.

    • Optimizing overseas access: Overseas network environments can be complex. Refer to Optimize server network latency to tune your integration and reduce network latency and request failures.

    China (Hong Kong)

    • Public endpoint: cloudauth-intl.cn-hongkong.aliyuncs.com

    • Internal endpoint: cloudauth-intl-vpc.cn-hongkong.aliyuncs.com

Online debugging and integration

Note

Before debugging and integration, read the Use OpenAPI document to learn how to call APIs on the OpenAPI platform and obtain the SDK.

Use OpenAPI Explorer to debug this operation online and generate SDK code examples.

Request parameters

Parameter

Type

Required

Description

Example

ProductCode

String

Yes

The product solution to use. The value must be MOBILE_2META.

MOBILE_2META

ParamType

String

Yes

The encryption type for the parameters. Valid values:

  • normal: The parameters are not encrypted (plaintext).

  • md5: The parameters are MD5-encrypted.

  • sm2: The parameters are SM2-encrypted.

Note
  • MD5 encryption: Each parameter's ciphertext must be a 32-character lowercase MD5 string. If your MD5-encrypted calls fail while plaintext calls succeed, try regenerating the ciphertext with a different MD5 tool, as outputs can vary.

  • SM2 encryption: For details on SM2 parameter encryption, see SM2 Encryption.

normal

UserName

String

Yes

The name.

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

  • If ParamType is set to md5, pass the 32-character lowercase MD5 ciphertext of the name.

  • If ParamType is set to sm2, pass the SM2 ciphertext of the name.

  • Plaintext: Zhang San

  • MD5 ciphertext: 32fa7bcd874161bea8ec8fd98f390ec9

  • SM2 ciphertext: MG8CIQCxI0wNYbc0c2BRL+7+tSethTXfQC391ZFnszRRcvRZ9AIgekQYhgDtxaDuoRD4bde/5fnFdlUp4YoxlEnIFLLm2mQEILkctuy6Rw6lfAUxBtkpPoPVCJAeD5al/RX8JFUvTACEBAYAgLJjBe0=

Mobile

String

Yes

The mobile number.

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

  • If ParamType is set to md5, pass the 32-character lowercase MD5 ciphertext of the mobile number.

  • If ParamType is set to sm2, pass the SM2 ciphertext of the mobile number.

  • Plaintext: 131****8888

  • MD5 ciphertext: 849169cd3b20621c1c78bd61a11a4fc2

  • SM2 ciphertext: MHUCIQDD5rrj8x5xZEXe9d2lI131M4Ql8bWmeMG+ba6KGT38xAIhAJErofLS0A/uMn/tU2lbHPRBnJKvDdLjJ5kARYOq4gHHBCBzZ3kecz1p80B8nPWNnQQMOkQeERWiOvLdhw/b7hjUZQQLqPBQkFGbfHZDCAE=

Response parameters

Parameter

Type

Description

Example

RequestId

String

The request ID.

130A2C10-B9EE-4D84-88E3-5384FF03****

Code

String

The response code. For details, see Server-side HTTP status codes.

Success

Message

String

A detailed description of the response code.

success

Result

BizCode

String

The verification result:

  • 1: Consistent. (Billed)

  • 2: Inconsistent. (Billed)

  • 3: No record found. (Not billed)

1

IspName

String

The carrier name:

  • CMCC: China Mobile

  • CU: China Unicom

  • CT: China Telecom

CMCC