Request structure

CloudMonitor APIs are remote procedure call (RPC) APIs. You can call these APIs by sending HTTP requests.

The request structure is as follows:


In this request URL:

  • Endpoint is a cloud service access point. The endpoint of CloudMonitor is For more information about the endpoints of each region, see Endpoint.
  • Action is an operation performed, such as calling the QueryMetricList API to query the monitoring data of an instance.
  • Version is the version of the API used. The current version is 2017-03-01.
  • Parameters are request parameters, which by convention are separated by ampersands (&). Request parameters consist of common parameters and API-specific parameters. Common parameters include the API version number, authentication information, among other information.

The following is an example of how to call the QueryMetricList API to query the monitoring data of an instance.


Region Endpoint
China East 1 (Hangzhou)
China East 2 (Shanghai)
China North 1 (Qingdao)
China North 2 (Beijing)
China South 1 (Shenzhen)
China North 3 (Zhangjiakou)
Hong Kong
Asia Pacific SE 1 (Singapore)
US West 1 (Silicon Valley)
US East 1 (Virginia)
EU Central 1 (Frankfurt)
Asia Pacific SE 2 (Sydney)
Middle East 1 (Dubai)
Asia Pacific NE 1 (Tokyo)
Asia Pacific SE 3 (Kuala Lumpur)
China North 5 (Hohhot)
Asia Pacific SE 5 (Jakarta)
Asia Pacific SOU 1 (Mumbai)
UK (London)
Note When you call the API operation for querying the monitoring data in Asia Pacific NE 1 (Tokyo), use the endpoint in China East 1 (Hangzhou).

API authorization

For better security, we recommend that you use a RAM user account to call API operations. However, before using a RAM account to call an SLB API operation, you must grant the RAM user the corresponding permission by creating an authorization policy and attaching that policy to the RAM user.

API signature

To ensure that API operations are securely called, Alibaba Cloud authenticates each API request by using an API signature. When you manually initiate an API request, follow the definition of RFC 2104, and use AccessSecret to evaluate the HMAC values, and use these values as signatures for the encoded and sorted entire request string. For more information, see Sign RPC APIs.

When calling an RPC API, you need to add the signature to your API request using the following format:


Consider the API operation QueryMetricList as an example, and assume that the Accesskey ID is testid and AccessKey Secret is testsecret. The request URL before the signature is as follows:{instanceId:'i-abcdefgh123456'}&Timestamp=2017-03-23T06:59:55Z&Project=acs_ecs_dashboard&SignatureVersion=1.0&Format=JSON&SignatureNonce=aeb03861-611f-43c6-9c07-b752fad3dc06&Version=2015-10-20&AccessKeyId=TestId&Metric=cpu_idle&SignatureMethod=HMAC-SHA1
The calculated signature string StringToSign is as follows:
Given that the AccessKey Secret is testsecret and the key used for HMAC calculation is testsecret&, the signature value is as follows:

Add the signature as a signature parameter to the URL request. The final URL is obtained as follows: