This topic provides an overview of Cloud Enterprise Network (CEN) API calls. After you call CEN APIs, HTTP GET requests are sent to the API endpoint of CEN, and the system responds according to the parameters set in the request. Note that both the request and the response are UTF-8-encoded.

Request syntax

CEN APIs use RPC style. To call CEN APIs, send HTTP requests.

The structure of a CEN API request is as follows:

  • Endpoint: the endpoint of the cloud resource involved. The endpoint of CEN is
  • Action: the name of this action. For example, if you need to query created CEN instances, the action is DescribeCens.
  • Version: the version of the API. The version of CEN APIs is 2017-09-12.
  • Parameters: the request parameters. Separate multiple parameters by using ampersands (&).

    Request parameters include common parameters and API-specific parameters. Common parameters include API version and identity authentication information among other parameters.

The following is an example of calling DescribeCens to query created CEN instances.
Note The following code has been edited to ease readability.

API authorization

To maintain account security, we recommend that you use the Access Keys (AKs) of RAM users to call APIs. Before you use a RAM user to call an API, you must grant the RAM user the corresponding permission to call the API by creating an authorization policy and attaching the policy to the RAM user.

For more information about the policies related to CEN APIs, see RAM authentication.

API signature

Authentication is required by the CEN service for each API call, which is provided by the inclusion of signature information in the request.

CEN uses an AccessKeyID and AccessKeySecret pair (that is, an AK) and symmetric encryption to authenticate the identity of the request sender. AKs are certificates that Alibaba Cloud issues to Alibaba Cloud accounts and RAM users for authentication. It is similar to a logon password. The AccessKeyID is used to identify the visitor's identity. The AccessKeySecret is the key used to encrypt the signature string. The server uses the AccessKeySecret to decrypt the signature string. The AccessKeySecret must be kept confidential.

For an RPC API, you must add the signature to the API request in the following format:


Take the API call of DescribeCens as an example. If your AccessKeyID is testid, and your AccessKeySecret is testsecret, the original request URL is as follows:
To generate the signature, follow these steps:
  1. Create the string to be signed by using the request parameter.
  2. Calculate the HMAC value of the string.

    Add an ampersand (&) after the AccessKeySecret to add the key of the HMAC value. In this example, the key is testsecret&.

  3. Add the signature to the request parameter.
    http:/ Action=DescribeCens