Skip to content

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 ​

  • 0 indicates success.
  • A non-0 value 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 CodeError MessageDescription
-1system errorSystem error
0okSuccess
54101API_Missing_Sud_TimestampMissing Sud timestamp
54102API_Missing_Sud_SignatureMissing Sud signature
54103API_Missing_Sud_AppIdMissing Sud app ID
54104API_Invalid_SignatureInvalid signature
54105API_Invalid_EncryptInvalid encryption
54106API_Invalid_Sud_AppIdInvalid Sud app ID
54107API_Invalid_Sud_AppIdMatchSud app ID mismatch
54108API_NoExist_DevSecretSymSymmetric key does not exist
54109API_NoExist_DevSecretAsymAsymmetric key does not exist
54201invalid grant_typeInvalid grant type
54202invalid app_idInvalid app_id
54203invalid secretInvalid secret
54210invalid gameidInvalid game ID
54211no linked gameGame not linked
54212no available game packageNo available game package found
54213missing data asymmetric keyMissing data asymmetric key
54221invalid sud trade noInvalid Sud trade number
54222invalid app reward query urlInvalid reward query URL
55001server busy, please retryServer busy, please retry

3. Troubleshooting Suggestions ​

  1. 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.
  2. For app credential errors (such as 54103, 54106, 54107, 54202, 54203), first verify the app ID, secret, backend configuration, and the current call environment.
  3. 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.
  4. For server busy (55001), retry later; if it persists, record the request ID, interface path, and time point, then investigate the service status.