Appendix1：Handling errors
The Information Dawsure Web Service uses standard HTTP response status codes to handle errors. It is common to send messages using error codes to explain the error in more detail so that problems it can fix or report can be resolved.
Appendix2：Error codes
All Dowsure web API parts are common error codes. For API specific error codes, refer to the corresponding error code section reference of the API.
Appendix3：Common HTTP error status codes
| Error code | HTTP status code | Description |
|---|---|---|
| InputStreamDisconnected | 400 | Error reading input stream. |
| InvalidParameterValue | 400 | Use an invalid parameter value, or the request size exceeds the maximum accepted size, or the request expires. |
| AccessDenied | 401 | Access denied. |
| InvalidAccessKeyId | 403 | Invalid AccessKeyID value used. |
| SignatureDoesNotMatch | 403 | The signature used does not match the calculated signature value of the server. |
| InvalidAddress | 404 | Use invalid path. |
| InternalError | 500 | Internal service failed. |
| ServerNnavailable | 503 | (Service unavailable) The server is currently unavailable (due to overloading or downtime for maintenance). Usually, this is only a temporary state. |
| GatewayTimeout | 504 | (Gateway timeout) The server acts as a gateway or proxy, but does not receive a request from the upstream server in time. |
| HttpIsNotSupported | 505 | The server does not support the HTTP protocol version used in the request. |
Appendix4：Unified response
| Field | Description | Required |
|---|---|---|
| code | Response Code | Required |
| data | Json Data | Required |
| msg | Information | Optional |