API Speicifcations
Last Updated：2020-07-20
Public Header
Public Request Header
| Public Header | Description |
|---|---|
| Authorization | Include the Access Key and request signature. |
| Content-Type | application/json; charset=utf-8. |
| x-bce-date | A string representing the date, which is in line with the API specifications. |
| x-bce-content-sha256 | A hexadecimal string representing the content of the SHA256 signature. The content here refers to the HTTP Request Payload Body, namely the original data before the content is encoded via the HTTP. |
The standard header fields of the HTTP protocol are not listed here. The public header field is required to appear in each DCC API. The x-bce-content-sha256 header field appears only in the POST and PUT requests. POST, PUT, DELETE and other request data are placed in the request body.
Public Response Header
| Public Header | Description |
|---|---|
| Content-Type | application/json; charset=utf-8. |
| x-bce-request-id | The DCC is generated at the backend, and automatically set to the response header field. |
The request id is generated by the DCC service with UUID version 4.