CompanyThreeElementsVerification

Updated at:

Used to verify a company name, company certificate number, and the name of the company's legal representative. Verification passes only when all three are consistent and the company's operating status is in business.

Operation description

  • Before you use this API, make sure that you have fully understood the billing method and pricing of the Three-Element Company Verification product. For billing details, see Billing.

  • In the returned result, charges apply when VerifyResult is true/false and ReasonCode is 0/1/2. No charges apply in other cases.

  • Before you use this API, log on to the Cell Phone Number Service console, go to the Tag Plaza page, find the corresponding tag, click Apply for Activation, and submit the application materials. 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. Requests that exceed this limit are throttled, which may affect your business. Call this API at a reasonable rate.

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:CompanyThreeElementsVerification

create

*All Resource

*

None None

Request parameters

Parameter

Type

Required

Description

Example

EpCertNo

string

Yes

The company certificate number.

9242032*******J627

EpCertName

string

Yes

The company name.

A Company

LegalPersonCertName

string

Yes

The name of the company's legal representative.

Note

If the company has multiple legal representatives, separate the names with the Chinese enumeration comma ("、").

Zhang San

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. Each request returns a unique ID, which can be used to troubleshoot and locate issues.

68A40250-50CD-034C-B728-0BD135850177

Message

string

The description of the returned status code.

OK

Data

object

The returned data.

DetailInfo

object

The company details.

{ "enterpriseStatus": "In Business (Open)", "openTime": "2023-05-25/2053-05-24" }

OpenTime

string

The business term of the company.

2023-05-25/2053-05-24

EnterpriseStatus

string

The operating status of the company.

In Business (Open)

InconsistentData

array

The fields whose verification results are inconsistent.

string

  • EpCertName: the company name

  • EpCertNo: the company certificate number

  • CertName: the name of the company's legal representative

CertName

VerifyResult

string

The verification result. Valid values:

  • true: The information is consistent and the company is operating normally.

  • false: The verification failed.

false

ReasonCode

integer

The verification result code. Valid values:

  • 0: The verification is consistent.

  • 1: The verification is consistent, but the company is not operating normally.

  • 2: The person-company verification is inconsistent.

  • 3: The two-element company verification failed.

  • 4: The company is not found.

  • 5: The person does not exist in the database.

2

Code

string

The request status code.

OK

Examples

Success response

JSON format

{
  "AccessDeniedDetail": "-",
  "RequestId": "68A40250-50CD-034C-B728-0BD135850177",
  "Message": "OK",
  "Data": {
    "DetailInfo": {
      "OpenTime": "2023-05-25/2053-05-24",
      "EnterpriseStatus": "在营(开业)"
    },
    "InconsistentData": [
      "CertName"
    ],
    "VerifyResult": "false",
    "ReasonCode": 2
  },
  "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.