CompanyFourElementsVerification-阿里云帮助中心

Verifies the enterprise name, enterprise certificate number, enterprise legal person name, and enterprise legal person ID card number. All four items must be consistent and the enterprise's operating status must be active for verification to pass.

Operation description

Before you use this API, make sure that you fully understand the billing method and prices of the Enterprise Four-Element Verification product. For billing details, see Product Billing.
Billing applies when VerifyResult returns true/false and ReasonCode is 0, 1, or 2 in the response. Billing does not apply in other cases.
Before you use this API, log on to the Cell Phone Number Service console, go to the Tag Square page, find the corresponding tag, click Apply to Activate, and submit your application. You can use the API after the application is approved.

QPS limit

The per-user QPS limit for this API is 200 calls per second. If the limit is exceeded, API calls are throttled, which may affect your business. Call the API appropriately.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

dytns:CompanyFourElementsVerification

get

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
EpCertNo	string	Yes	The enterprise certificate number.	9242032*******J627
EpCertName	string	No	The enterprise name (required).	A company
LegalPersonCertName	string	Yes	The name of the enterprise legal person. Note If the enterprise has multiple legal persons, separate them with a Chinese enumeration comma ("、").	Zhang San
LegalPersonCertNo	string	Yes	The ID card number of the enterprise legal person. Note If the enterprise has multiple ID card numbers, separate them with a Chinese enumeration comma ("、").	610321******0011、510180******0022
AuthCode	string	Yes	The authorization code. Note Log on to the Cell Phone Number Service console and go to the My Applications page to obtain the authorization ID, which is the authorization code.	Dd1r***4id

Response elements

Element	Type	Description	Example
	object
AccessDeniedDetail	string	The details about the access denial.	-
RequestId	string	The common parameter. The ID returned for each request is unique and can be used to troubleshoot and locate issues.	CC3BB6D2-2FDF-4321-9DCE-B38165CE4C47
Message	string	The description of the returned status code.	OK
Data	object	The structure.
DetailInfo	object	The enterprise details.	{ "enterpriseStatus": "In operation (open)", "openTime": "2023-05-25/2053-05-24" }
OpenTime	string	The business term of the enterprise.	2023-05-25/2053-05-24
EnterpriseStatus	string	The operating status of the enterprise.	In operation (open)
InconsistentData	array	The fields that failed verification.
	string	EpCertName: enterprise name EpCertNo: enterprise certificate number CertName: enterprise legal person name CertNo: enterprise legal person certificate number	CertName
VerifyResult	string	The verification result. Valid values: true: The information is consistent and the enterprise is operating normally. false: Verification failed.	true
ReasonCode	integer	The verification result code. Valid values: 0: Verification passed. 1: Verification passed, but the enterprise is not operating normally. 2: The legal person and enterprise information are inconsistent. 3: The enterprise four-element verification failed. 4: The enterprise was not found. 5: The legal person was not found in the database.	0
Code	string	The request status code.	OK

Examples

Success response

JSON format

{
  "AccessDeniedDetail": "-",
  "RequestId": "CC3BB6D2-2FDF-4321-9DCE-B38165CE4C47",
  "Message": "OK",
  "Data": {
    "DetailInfo": {
      "OpenTime": "2023-05-25/2053-05-24",
      "EnterpriseStatus": "在营（开业）"
    },
    "InconsistentData": [
      "CertName"
    ],
    "VerifyResult": "true",
    "ReasonCode": 0
  },
  "Code": "OK"
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidParameter	Invalid parameter.
400	AuthCodeIllegal	Illegal authCode.
500	RequestTimeout	Request supplier timed out.	Request supplier timeout
500	RequestSupplierError	Request supplier error.	Request supplier error.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.