| Error Code | Error Msg | Meaning |
|---|---|---|
| 200 | ok | Success |
| 400 | request header param invalid | First-level JSON parameter issue Suggestions: 1、Check if the JSON structure is complete. 2、Ensure all required fields are correctly included. 3、Validate that the data field is a valid object type. 4、Verify the presence of key fields like trace. |
| 400 | request data param invalid | Invalid data field parameter in JSON request Suggestions: 1、Check if the data field is a valid object. 2、Ensure all required fields in data are correctly filled. 3、Verify the content of the data field against the specific API documentation. 4、Pay special attention to POST requests, ensuring the JSON parameters in the body are complete and correct. |
| 401 | token invalid | Token is invalid Possible Causes: 1、Incorrect token format. 2、Token account has expired. |
| 402 | query invalid | Invalid query parameters in request Suggestions: 1、Check the query parameters in the GET request. 2、URL-encode the query parameters. 3、Ensure the parameter format meets API requirements. 4、Verify that special characters are correctly escaped. |
| 429 | rate limit | Exceeded the subscribed plan's request frequency Suggestions: 1、Optimize request frequency and logic. 2、Consider upgrading your plan for a higher request frequency. |
| 600 | code invalid | Request code product is invalid Suggestions: 1、Check the Request URL: Carefully verify the API documentation, as the request URLs for stock and forex/precious metals data are different. 2、Check the Product Code: Refer to the product list to ensure the code is valid and accurate: Product List |
| 601 | body empty | The request message body data is empty Suggestions: 1、Check the message body of the POST request. 2、Ensure the body contains complete JSON parameters. 3、Pay special attention to batch retrieval interfaces like /batch-kline. 4、Verify that all required fields are correctly filled. |
| 603 | token level not enough | Requested number of products or K-lines exceeds API limits Suggestions: 1、Check Product Count: Ensure the number of requested products is within the plan limit. 2、Validate K-line Requests: Confirm the K-line count meets API specifications. Batch requests allow only 2 K-lines at a time. |
| 604 | code unauthorized | Your token does not have permission to access this code. |
| 605 | too many requests | Generally, it is the Http interface request frequency limit Suggestions: 1、Optimize request frequency and logic. 2、Consider upgrading your plan for higher request frequency. |
| 606 | too many requests and connection will be closed | Generally, it is the Websocket interface request frequency limit Suggestions: 1、Check WebSocket Connections: Ensure you do not exceed the maximum connections allowed by your plan. 2、Control Request Frequency: Ensure a minimum interval of 3 seconds between multiple WebSocket requests. |