Request structure

CloudMonitor APIs belong to the RPC type. You can call CloudMonitor  APIs by sending HTTP requests.

The request structure is as follows:


In this syntax,

  • Endpoint is the cloud service node that is called. The access node is For the endpoint of each region, see Endpoint.

  • Action is an action to perform, such as querying the monitoring data for an instance using QueryMetricList.

  • Version is the version of the API, and the current version is 2017-03-01.

  • Parameters are the request parameters seperated by &

    Request parameters consist of common parameters and API specific parameters. Common parameters include the API version number, authentication information, and other information.

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


Region Service address
East China 1 (Hangzhou)
China East 2 (Shanghai)
North China 1 (Qingdao)
China North 2 (Beijing)
China South 1 (Shenzhen)
China North 3 (Zhangjiakou)
China (Hong Kong)
US (Silicon Valley)
US (Virginia)
Central Europe 1 (Frankfurt)
Australia (Sydney)
Middle East 1 (Dubai)
Asia Pacific NE 1 (Tokyo)
Malaysia (Kuala Lumpur)
China (Hohhot)
Asia Pacific SE 5 (Jakarta)
Note When you call the APIs at Asia Pacific NE 1 (Japan), the actual API server in service is East China 1 (Hangzhou).

API authorization

For the security of your account, we recommend that you use a RAM user to call APIs. Before using 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.

API signature

To ensure secure calls to the API, when the API is invoked, Ali cloud authenticates each API request through the signature. When you manually launch an API request, follow the definition of RFC 2104, use AccessSecret to evaluate the HMAC values as signatures for the encoded, sorted entire request string. For more information, seeRPC API signature.

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


Take  QueryMetricList as an example, assume that the Accesskey ID is testid, AccessKey Secret is testsecret, The request URL before signature:{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 StringToSign:
Because AccessKey Secret is testsecret, and the key used for HMAC calculation is testsecret&, the signature value is

Add signature to URL request as a Signature parameter to get the final URL: