Enterprise element verification

Updated at:

This topic describes how to use the enterprise element verification API to verify the consistency and authenticity of enterprise information.

Basic information

API name: EntElementVerify

service endpoint: cloudauth.aliyuncs.com

request method: POST and GET

protocol: HTTPS

description: Verifies the consistency and authenticity of enterprise information.

Note

This service supports enterprises and sole proprietorships.

QPS limit: This API has a dedicated QPS limit. For more information, see QPS limits for Enterprise Identity Recognition APIs.

Request parameters

Parameter

Type

Required

Description

Example

SceneCode

String

Yes

A custom scene code of up to 32 letters, digits, and underscores (_) used to distinguish between business scenarios.

1000000006

MerchantBizId

String

Yes

A unique business ID for the request, used for troubleshooting. The ID must be unique for each request and can contain up to 32 letters and digits.

e0c34a77f5ac40a5aa5e6ed20c35****

MerchantUserId

String

Yes

The user ID from your business system, which can contain up to 32 letters and digits.

mch7x9a2b4c8d3e5f6g1h2i3j4k5****

UserAuthorization

String

Yes

Indicates whether you have obtained user authorization.

  • 1: Authorized

  • 0: Unauthorized

1

InfoVerifyType

String

Yes

The type of enterprise element verification.

  • ENT_2META: two-element verification

    Enterprise name + unified social credit code

  • ENT_3META: three-element verification

    Enterprise name + unified social credit code + name of the legal representative or person in charge

  • ENT_4META: four-element verification

    Enterprise name + unified social credit code + name of the legal representative or person in charge + ID card number of the legal representative

ENT_2META

LicenseNo

String

Yes

The unified social credit code.

91330106673959****

EntName

String

Yes

The enterprise name.

**** Co., Ltd.

LegalPersonName

String

No

The name of the legal representative.

Note

This parameter is required for three-element and four-element verification.

Zhang**

LegalPersonCertNo

String

No

The ID card number of the legal representative.

Note

This parameter is required for four-element verification.

1******************9

Response parameters

Parameter

Type

Description

HTTP status code

Integer

The HTTP status code of the response.

HTTP Body

RequestId

String

The request ID.

Code

String

The status code. For more information, see Status codes.

Message

String

The detailed response message.

Result

BizCode

String

The verification result code:

  • 1: Matched

  • 2: Mismatched

  • 3: Not found

ReasonCode

String

The reason code. Valid values:

  • 100: Matched

  • 201: Person-enterprise mismatch

  • 202: Enterprise two-element mismatch

  • 301: Enterprise not found and cannot be verified

  • 302: Legal representative not found in the database

Note

This parameter was deprecated on June 15, 2023. This change does not affect existing integrations.

ReasonDetail

String

Details about inconsistencies. Multiple values are separated by commas.

  • LegalPersonNameFlag: The name of the legal representative is inconsistent.

  • LegalPersonCertNoFlag: The ID card number of the legal representative is inconsistent.

  • EntNameFlag: The enterprise name is inconsistent.

  • LicenseNoFlag: The unified social credit code is inconsistent.

Note

Example: LegalPersonNameFlag,LegalPersonCertNoFlag

Status

String

The business status.

  • 1: Active (In business)

  • 2: Moved out

  • 3: Canceled

  • 4: Revoked

  • 5: Rescinded

  • 6: Suspended

  • 0: Other

OpenTime

String

The validity period of the business license.

  • Format: yyyy-MM-dd/yyyy-MM-dd.

  • Example: 2018-09-25/9999-09-09.

Status codes

HTTP status code

Code

Description

200

Success

The request was successful.

400

MissingParameter

A required parameter is missing.

400

InvalidParameter

A parameter is invalid.

403

Forbidden.AccountAccessDenied

You do not have permission to access this resource. The service might not be activated or your account may have an overdue payment.

403

Forbidden.RAMUserAccessDenied

The RAM user is not authorized. Grant the AliyunYundunCloudAuthFullAccess permission to the RAM user.

403

Forbidden.NoUserAuthorization

User authorization was not obtained.

500

InternalError

An internal error occurred. Try the request again. If the error persists, record the request ID and contact technical support.

SDKs and code examples

OpenAPI Explorer and SDK Example

  • In OpenAPI Explorer, find SDK call examples on the right side of the API debugging page. Click SDK Installation in the upper-right corner of a code example to view installation information.

    Note

    Select your required programming language.

  • For an offline installation, go to the SDK Installation Page, select the SDK for your Required Language, and navigate to the release page to download it.