CompanyTwoElementsVerification

Updated at:

You can use this operation to verify a company's name and certificate number. The verification passes only if the name and certificate number match and the company is active.

Operation description

  • Before you call this operation, understand the billing methods and pricing of the company two-element verification service. For more information about billing, see Product Billing.

  • You are charged for the API call if the Code parameter in the response is OK and the ReasonCode parameter is 0, 1, or 3. You are not charged in other cases.

  • Before you use this operation, log on to the Cell Phone Number Service console. On the Tag Square page, find the required tag and click Request Access. Complete the application. You can use the service after your application is approved.

QPS limits

The queries per second (QPS) limit for a single user on this operation is 200 calls per second. If the limit is exceeded, API calls are throttled. This may affect your business. Plan your calls accordingly.

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

create

*All Resource

*

None None

Request parameters

Parameter

Type

Required

Description

Example

EpCertNo

string

Yes

The certificate number of the company.

9242032*******J627

EpCertName

string

Yes

The name of the company.

某企业

AuthCode

string

Yes

The authorization code.

Note

Log on to the Cell Phone Number Service console. On the My Applications page, 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 ID of the request.

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

Message

string

The message returned for the request.

OK

Data

object

The data returned.

DetailInfo

object

The details of the company.

Note

This field is not returned for public institutions or civil organizations.

{ "enterpriseStatus": "在营(开业)", "openTime": "2023-05-25/2053-05-24" }

OpenTime

string

The business term of the company.

2023-05-25/2053-05-24

EnterpriseStatus

string

The business status of the company.

在营(开业)

InconsistentData

array

The fields that failed the verification.

string

  • EpCertName: the company name

  • EpCertNo: the company certificate number

EpCertName

VerifyResult

string

The verification result. Valid values:

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

  • false: The verification failed.

Note

For public institutions and civil organizations, this operation does not verify the business status. It only verifies whether the company name and certificate number are consistent.

true

ReasonCode

string

The code of the verification result. Valid values:

  • 0: The verification is successful.

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

  • 3: The two-element verification for the company failed.

  • 4: The company is not found.

0

Code

string

The status code of the request.

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": [
      "EpCertName"
    ],
    "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 for a complete list.

Release notes

See Release Notes for a complete list.