Public parameters

Last Updated: Feb 15, 2017

Public request headers

Public request parameters are the request parameters that every interface must use.

Parameter name Description Required?
Authorization Authentication information used to verify the validity of a request, in the format of AccessKeyId:Signature. Required
Content-Length Content length of an HTTP request, which is defined in RFC 2616. Required
Content-Type Content type of an HTTP request, which is defined in RFC 2616. Required
Content-MD5 Base64-encoded 128-bit MD5 hash value of the HTTP message body. It is recommended that Content-MD5 be added to all requests to prevent request tampering. Required
Date Construction time of a request. At present, only the GMT format is supported. If the difference between the construction time and the MNS server time exceeds 15 minutes, invalid request is returned. Required
Host Host access value, for example, Required
Accept Return-value type required by the client. Options: application/json and application/xml. Required
x-acs-version API version. The current version is 2015-12-15. Required
x-acs-region-id A region indicates the physical location of an ECS instance. For more details, refer to Region. Required
x-acs-signature-nonce Unique random number, used to prevent replay attacks. Different random numbers must be used for different requests. Required
x-acs-signature-method Signature method, which can only be HMAC-SHA1. Required


  1. GET /clusters HTTP/1.1
  2. Host:
  3. Accept: application/json
  4. User-Agent: cs-sdk-python/0.0.1 (Darwin/15.2.0/x86_64;2.7.10)
  5. x-acs-signature-nonce: f63659d4-10ac-483b-99da-ea8fde61eae3
  6. Authorization: acs ACSbW2iBbyX0Pk9N:mp/6Wdr18V3qAc5gbgsqMe/iB0c
  7. x-acs-signature-version: 1.0
  8. Date: Wed, 16 Dec 2015 11:18:47 GMT
  9. x-acs-signature-method: HMAC-SHA1
  10. Content-Type: application/json;charset=utf-8
  11. X-Acs-Region-Id: cn-beijing
  12. Content-Length: 0

Public return headers

Each time you send a request to call an interface, the system will return a unique identification code (RequestId) to you, no matter the request is successful or not.


XML example:

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!—Result root node-->
  3. <Interface name+Response>
  4. | <!—Return request tag-->
  5. | <RequestId>4C467B38-3910-447D-87BC-AC049166F216</RequestId>
  6. | <!—Return result data-->
  7. </Interface name+Response>

JSON example:

  1. {
  2. "RequestId": "4C467B38-3910-447D-87BC-AC049166F216"
  3. /* Return result data*/
  4. }
Thank you! We've received your feedback.