Server API Error Codes
This document summarizes the error codes that the APP server may receive when calling the OpenPaaS server API. When an interface returns a failure, you can use the error code and error message in the response body to locate the issue, then investigate together with the current interface parameters, authentication credentials, and signature/encryption configuration.
1. Error Code Notes
0indicates success.- A non-
0value indicates failure, which should be handled together with the error message returned by the interface and the current call context. - "Error Message" is the English error description returned by the server; "Description" is the corresponding meaning.
2. Error Code Table
| Error Code | Error Message | Description |
|---|---|---|
| -1 | system error | System error |
| 0 | ok | Success |
| 54101 | API_Missing_Sud_Timestamp | Missing Sud timestamp |
| 54102 | API_Missing_Sud_Signature | Missing Sud signature |
| 54103 | API_Missing_Sud_AppId | Missing Sud app ID |
| 54104 | API_Invalid_Signature | Invalid signature |
| 54105 | API_Invalid_Encrypt | Invalid encryption |
| 54106 | API_Invalid_Sud_AppId | Invalid Sud app ID |
| 54107 | API_Invalid_Sud_AppIdMatch | Sud app ID mismatch |
| 54108 | API_NoExist_DevSecretSym | Symmetric key does not exist |
| 54109 | API_NoExist_DevSecretAsym | Asymmetric key does not exist |
| 54201 | invalid grant_type | Invalid grant type |
| 54202 | invalid app_id | Invalid app_id |
| 54203 | invalid secret | Invalid secret |
| 54210 | invalid gameid | Invalid game ID |
| 54211 | no linked game | Game not linked |
| 54212 | no available game package | No available game package found |
| 54213 | missing data asymmetric key | Missing data asymmetric key |
| 54221 | invalid sud trade no | Invalid Sud trade number |
| 54222 | invalid app reward query url | Invalid reward query URL |
| 55001 | server busy, please retry | Server busy, please retry |
3. Troubleshooting Suggestions
- For signature and encryption errors (such as
54101,54102,54104,54105), first check whether the request headers, timestamp, signature algorithm, encryption parameters, and key configuration are consistent. - For app credential errors (such as
54103,54106,54107,54202,54203), first verify the app ID, secret, backend configuration, and the current call environment. - For business parameter or configuration errors (such as
54201,54210,54211,54212,54213,54221,54222), check the request parameters, game linkage, game package, and data key configuration against the specific API documentation. - For server busy (
55001), retry later; if it persists, record the request ID, interface path, and time point, then investigate the service status.
