1. When a developer calls API, three categories of errors may occur: API platform errors, ISV business errors and container errors. The following describes the terms related to the ISV success rate:
2. The errors from connecting Taobao server mainly involve http connection errors or connections reset or rejected, etc. They occur when a developer gains access to Taobao server. Contact a server administrator or use the Internet to search for solutions.
API platform errors mainly fall into two categories:
1. Call errors with an error code being less than 100 (excluding error codes 15, 40, 41): These errors usually occur, because the request from a user does not fulfill the basic verification. When encountering such errors, check the authority, frequency and other conditions of the applications. Then, check the uploaded parameters for completeness and validity based on the document.
2. Call errors with a sub-error code (sub_code) starting with “isp.”: These errors usually occur, because the server operates abnormally. When encountering such errors, try again some time later.
Platform errors with an error code being less than 100
|
Platform sub errors
|
1. ISV business errors result from missing or incorrect parameters uploaded by ISV, or from incorrect formats of these parameters, etc. For this reason, the ISV shall check whether the corresponding information is uploaded based on the error information. It is recommended to try again after correcting such errors.
Two categories are involved mainly:
2. An error response directly presents the failed interaction between the user and the server. When the ISV fails to call the top service, keep the error log for future retrieval if possible.
3. Errors with error codes 40 and 41
|
4. Business sub errors
|
Information about parent error codes
Error code |
English |
Description |
Solution |
53 |
Insufficient security level |
Insufficient security level. |
Improve the application security level, or refresh the authorization security level. |
Information about sub error codes
Sub error code |
Description |
Owner |
Solution |
high-risk security breach |
The high-risk security breach exists. |
ISV |
Re-publish after solving the security breach. |
mid-risk security breach |
The mid-risk security breach exists. |
ISV |
Re-publish after solving the security breach. |
R1 security authorize missing |
The R1-level authorization is not provided. |
ISV |
Provide the R1-level authorization (the user is authorized again, or the authorization is refreshed). |
R1 security authorize invalid |
The R1-level authorization is invalid. |
ISV |
Provide the R1-level authorization (the user is authorized again, or the authorization is refreshed). |
R2 security authorize missing |
The R2-level authorization is not provided. |
ISV |
Provide the R2-level authorization (the user is authorized again, or the authorization is refreshed). |
R2 security authorize invalid |
The R2-level authorization is invalid. |
ISV |
Provide the R2-level authorization (the user is authorized again, or the authorization is refreshed). |
W1 security authorize missing |
The W1-level authorization is not provided. |
ISV |
Provide the W1-level authorization (the user is authorized again, or the authorization is refreshed). |
W1 security authorize invalid |
The W1-level authorization is invalid. |
ISV |
Provide the W1-level authorization (the user is authorized again, or the authorization is refreshed). |
W2 security authorize invalid |
The W2-level authorization is not provided. |
ISV |
Provide the W2-level authorization (the user is authorized again, or the authorization is refreshed). |
W2 security authorize invalid |
The W2-level authorization is invalid. |
ISV |
Provide the W2-level authorization (the user is authorized again, or the authorization is refreshed). |
|