Error Codes
Error codes have two layers. The outer code reflects the API-layer result, and data.bizCode reflects the business result. A call is successful only when both code == 0 and data.bizCode == 0. See Unified response structure.
API error codes (code)
| code | Description | Suggestion |
|---|---|---|
| 0 | Success | — |
| 401 | Authentication failed | Find the specific cause in the table below |
| 429 | Too Many Requests | Lower the call rate and retry; each API allows up to 10 requests / second |
Causes of 401
| Message | Meaning | Suggestion |
|---|---|---|
| Missing required headers | A required request header is missing | Check that all Common request headers are present |
| Invalid timestamp format | The timestamp format is incorrect | X-Timestamp must be a timestamp in seconds |
| Request timestamp expired | The request timestamp has expired | Synchronize the server clock and send the request again |
| Invalid nonce format | The nonce does not meet the format rule | Must match ^[A-Za-z0-9]{16,32}$ |
| Nonce already used or validation failed | The nonce was already used or failed validation | Use a new random string for every request; never reuse it |
| appId not found | The appId does not exist | Check APP-ID |
| appId is disabled | The appId has been disabled | Contact technical support |
| Signature calculation failed | Signature calculation failed | Check your signature implementation; see Signature mechanism |
| Signature verification failed | Signature verification failed | Check the concatenation order of the string to sign, that path includes the /open-apis prefix, and that timestamp and nonce match the headers |
Business error codes (bizCode)
| bizCode | Description |
|---|---|
| 0 | Success |
| 10000001 | Invalid parameters |
| 10000003 | Too many requests. Please wait and try again |
| 10000103 | The system service is abnormal, please contact customer service |
| 100027001 | Invalid credit operation parameters |
| 100027003 | Insufficient credit balance |
| 100041003 | Spatial modeling task does not exist |
| 100041004 | Spatial modeling result not found |
| 100041006 | Space not found |
| 100041010 | AppId does not have spatial modeling permission |
| 100041016 | Task status [modeling], deletion is not allowed |
| 100041017 | Task cannot be canceled in its current status |
Troubleshooting failed modeling
When a task enters Modeling failed (9), call Paginated Task List or Task Details and read errorCode and failedReason to find the cause.
These two fields carry failure information from inside the modeling pipeline and use a different set of values from bizCode above. When an API call succeeds but the task fails to model, bizCode is still 0.