Status Codes and Retry Policies

To ensure reliability, the API call success rate should hit 99.99%. If errors arise during API access, it is recommended to implement a retry strategy. For short-term issues, retry up to three times within six hours. For persistent problems, attempt one retry at an interval of one minute over the same period.
Table 1 describes the HTTP status codes and retry policies.
Status Code |
Message |
Description |
Retry Policy |
---|---|---|---|
100 |
Continue |
Continue sending requests. This temporary response is used to inform the client that initial part of the request has been received and has not yet been rejected by the server. |
Retry up to three times within six hours. |
101 |
Switching Protocols |
Switching protocols. The target protocol must be more advanced than the original one. For example, the protocol in use is switched to a later version of HTTP. |
Retry is not performed. |
200 |
OK |
The request was successfully processed. It is generally used for GET and POST requests. |
Retry is not performed. |
201 |
Created |
The request has been fulfilled and has resulted in one or more new resources being created. |
Retry is not performed. |
202 |
Accepted |
The request has been accepted for processing, but the processing has not been completed. |
Retry is not performed. |
203 |
Non-Authoritative Information |
The request was successful but the response has been modified by a transforming proxy. |
Retry is not performed. |
204 |
NoContent |
The server has successfully fulfilled the request, but did not return any response body. The status code is returned in response to an HTTP OPTIONS request. |
Retry is not performed. |
205 |
Reset Content |
The server has fulfilled the request and requires the client to reset the content. |
Retry is not performed. |
206 |
Partial Content |
The server has fulfilled a range GET request. |
Retry up to three times within six hours |
300 |
Multiple Choices |
There are multiple options for the requested resource. The response contains a list of resource characteristics and addresses from which the customer or customer agent (such as a browser) can choose the most appropriate one. |
Retry is not performed. |
301 |
Moved Permanently |
The requested resource has been assigned with a new permanent URI. This new URI is contained in the response. |
Retry is not performed. |
302 |
Found |
The requested resource resides temporarily under a different URI. |
Retry is not performed. |
303 |
See Other |
The response to the request can be found under a different URI. It is expected to be accessed using a GET or POST method. |
Retry is not performed. |
304 |
Not Modified |
The requested resource has not been modified. When the server returns this status code, it does not return any resources. |
Retry is not performed. |
305 |
Use Proxy |
The requested resource must be accessed through a proxy. |
Retry is not performed. |
306 |
Unused |
This HTTP status code is no longer used. |
Retry is not performed. |
400 |
BadRequest |
Invalid request. Modify the request and retry. |
Retry is not performed. |
401 |
Unauthorized |
The status code is returned after the client provides the authentication information, indicating that the authentication information is incorrect or invalid. |
Retry up to three times within six hours |
402 |
Payment Required |
This status code is reserved for future use. |
Retry is not performed. |
403 |
Forbidden |
The request has been rejected. The server has received and understood the request; yet it refused to respond, because the request is set to deny access. Do not retry the request before modification. |
Retry is not performed. |
404 |
NotFound |
The requested resource could not be found. Modify the request and retry. |
Retry is not performed. |
405 |
MethodNotAllowed |
The request contains one or more methods not supported by the resource. Modify the request and retry. |
Retry is not performed. |
406 |
Not Acceptable |
The server cannot fulfill the request according to the content characteristics of the request. |
Retry is not performed. |
407 |
Proxy Authentication Required |
This status code is similar to 401, but the client must be authenticated using a proxy. |
Retry is not performed. |
408 |
Request Time-out |
The client does not produce a request within the time that the server was prepared to wait. The client may repeat the request without modifications at any time later. |
Attempt one retry at an interval of one minute within six hours. |
409 |
Conflict |
The request cannot be processed due to a conflict. The resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request. |
Retry is not performed. |
410 |
Gone |
The requested resource is no longer available. The requested resource has been deleted permanently. |
Retry is not performed. |
411 |
Length Required |
The server fails to process the request which does not contain the Content-Length header field. |
Retry is not performed. |
412 |
Precondition Failed |
The server does not meet one of the requirements that the requester puts on the request. |
Retry is not performed. |
413 |
Request Entity Too Large |
The request is larger than that the server can process. The server may close the connection to prevent the client from continuously sending the request. If the server cannot process the request temporarily, the response will contain a Retry-After header field. |
Retry is not performed. |
414 |
Request-URI Too Large |
The Request-URI is too long for the server to process. |
Retry is not performed. |
415 |
Unsupported Media Type |
The server cannot process the media format in the request. |
Retry is not performed. |
416 |
Requested range not satisfiable |
The requested range is invalid. |
Retry is not performed. |
417 |
Expectation Failed |
The server fails to meet the requirements of the Expect request header field. |
Retry is not performed. |
422 |
UnprocessableEntity |
The request is well-formed but is unable to be processed due to semantic errors. |
Retry is not performed. |
429 |
TooManyRequests |
Too many requests have been made within the allowed time. In this case, the client should retry after the time period specified in the Retry-After response header. |
Attempt one retry at an interval of one minute within six hours. |
500 |
InternalServerError |
The server is able to receive the request but unable to understand it. |
Attempt one retry at an interval of one minute within six hours. |
501 |
Not Implemented |
The server does not support the function required to fulfill the request. |
Retry is not performed. |
502 |
Bad Gateway |
The server was acting as a gateway or proxy and received an invalid request from a remote server. |
Retry is not performed. |
503 |
ServiceUnavailable |
The requested service is invalid. Modify the request and retry. |
Retry is not performed. |
504 |
ServerTimeout |
The request cannot be fulfilled within a given amount of time. The response will reach the client only if the request carries a timeout parameter. |
Attempt one retry at an interval of one minute within six hours. |
505 |
HTTP Version not supported |
The server does not support the HTTP protocol version used in the request. |
Retry is not performed. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.