Common request parameters are used to identify general information such as the API operation to be called, user identity, and signature. These parameters must be included in each API request. If not necessary, these parameters are no longer described in each individual interface document.
Common request parameters
The public request parameters should be carried in the request as the message header (header) of the HTTP request. The specific values are as follows:
| Parameter | Required | Description |
| x-acs-action | Yes | The name of the API. For more information about the value, seeCommunication monitoring. |
| x-acs-version | Yes | The version of the API operation in the YYYY-MM-DD format. Example: 2018-01-01. |
| x-acs-signature-nonce | No | A unique, random number used to prevent replay attacks. You must use different numbers for different requests. |
| x-acs-signature-method | Yes if the request is non-anonymous | The user signature method. Currently, HMAC-SHA1 is supported. |
| Authorization | Yes if the request is non-anonymous | The authentication information used to verify the validity of the request, in the format of acs AccessKeyId:Signature. The AccessKey ID is the AccessKey ID of the user. The Signature parameter is the request signature. For more information, see Signature. |
| Date | Yes | The specified Greenwich Mean Time (GMT) in HTTP 1.1, for example, Tue 9 Apr 2019 07:35:29 GMT. |
| Accept | No | The type of the return value required by the client. Valid values:
|
| Content-MD5 | No | The Base64-encoded 128-bit MD5 hash value of the HTTP request body. |
该文章对您有帮助吗？