API Speicifcations
Last Updated:2020-07-20
Public Request Header
The public header fields carried by all SCS for Redis API are listed in the following table. The standard header fields of the HTTP protocol are not listed here.The standard header field of HTTP protocol is no longer listed here.
Header field (Header) | Required | Description |
---|---|---|
Authorization | Required | Include Access Key and request signature |
Content-Type | Optional | application/json; charset=utf-8 |
x-bce-date | Optional | String representing date, conforming to API specification. |
x-bce-content-sha256 | Optional | Hexadecimal string representing SHA256 signature of content part. Content here refers to the HTTP Request Payload Body. It is the original data before the Content part is encoded by HTTP. |
The public header field appears in each SCS API, which is a required header field. The “x-bce-content-sha256” header field appear only in POST and PUT requests.
POST, PUT, DELETE and other request data are placed in request body.
Public Response Header
The public response header fields carried by all SCS for Redis API are listed in the following table. The standard response header fields of the HTTP protocol are not listed here.
Header field (Header) | Description |
---|---|
Content-Type | Only support JSON format, application/json; charset=utf-8 |
x-bce-request-id | SCS is generated at backend, and is automatically set to the response header field. |
The “request id” is generated by SCS service with UUID version4.