| Error Code | Error Content | Meaning |
|---|---|---|
| 200 | ok | Success |
| 400 | request header param invalid | The first-level parameters of the request JSON are invalid. Troubleshooting suggestions: 1. Check whether the JSON structure is complete. 2. Confirm that all required fields are included correctly. 3. Verify that the data field is a valid object. 4. Check whether key fields such as trace exist. |
| 400 | request data param invalid | The data field parameters in the request JSON are invalid. Troubleshooting suggestions: 1. Check whether the data field is a valid object. 2. Confirm that all required fields in data are filled in correctly. 3. Compare the data field content with the specific interface documentation. 4. For POST requests, pay special attention to whether the JSON parameters in the body are complete and correct. |
| 401 | token invalid | The token is invalid. Possible causes: 1. The Token format is incorrect. 2. The Token account has expired. |
| 402 | query invalid | The query parameter of the request is invalid. Troubleshooting suggestions: 1. Check the query parameter of the GET request. 2. URL-encode the query parameter. 3. Ensure that the parameter format meets the interface requirements. 4. Verify that special characters are escaped correctly. |
| 429 | Too Many Requests | The request frequency exceeds the limit specified by the plan. Suggestions: 1. Optimize the request frequency and logic. 2. Consider upgrading the plan to obtain a higher request frequency. Interface restriction pages: HTTP Interface Restrictions WebSocket Interface Restrictions Common scenario: For the Basic plan, if /kline is requested at least twice within one second, the first request succeeds and the second request returns 429 Too Many Requests, because the Basic plan allows only one /kline request per second. |
| 600 | code invalid | The requested product code is invalid. Troubleshooting suggestions: 1. Check the request URL. Stock data and forex/precious-metals data use different request URLs. 2. Check the product code. Compare it with the product list and make sure it is valid and accurate: Product List |
| 601 | body empty | The request body data is empty. Troubleshooting suggestions: 1. Check the body of the POST request. 2. Ensure that the body contains complete JSON parameters. 3. Pay special attention to batch interfaces such as /batch-kline.4. Verify that all required fields are filled in correctly. |
| 603 | token level not enough | The number of requested products or K-lines exceeds the limit specified in the interface documentation. Troubleshooting suggestions: 1. Check the number of products. For K-line interfaces, confirm whether the total of product count and K-line type count exceeds the plan limit. For non-K-line interfaces, confirm whether the requested product count exceeds the plan limit. 2. Verify the K-line request. Confirm that the number of K-lines complies with the interface rules. The batch product K-line interface allows only 2 K-lines per request. Interface restriction page: HTTP Interface Restrictions |
| 604 | code unauthorized | Your token does not have permission to request this code. |
| 605 | too many requests | Request frequency limit. Suggestions: 1. Optimize the request frequency and logic. 2. Consider upgrading the plan to obtain a higher request frequency. Interface restriction pages: HTTP Interface Restrictions WebSocket Interface Restrictions |
| 606 | too many requests and connection will be closed | Usually caused by WebSocket interface request frequency limits. Troubleshooting suggestions: 1. Check the number of WebSocket connections and confirm whether it exceeds the maximum number allowed by the plan. 2. Control the request frequency and ensure that multiple WebSocket requests are at least 3 seconds apart. Interface restriction page: WebSocket Interface Restrictions |
AllTick Website
Official website: https://alltick.co/