Skip to main content

1. Frequency Limits

2. IP Limits

  • HTTP interfaces limit request frequency only by Token and do not restrict IP addresses.
  • Example: the Basic plan allows one request per second. If a Token requests /kline once at 14:03:01 and calls /trade-tick once in the same minute, the backend service will respond normally. If the same Token sends two /kline requests within 14:03:01, the first request will be served normally and the second request will receive an error response.

3. K-line Query Limits

  • /kline: each query request can request K-line data for only one product code. Each query returns at most 500 K-lines. If more than 500 K-lines are requested, the system queries and returns 500.
  • /batch-kline: each query request can request K-line data for multiple product codes. The number of code/type groups allowed per batch varies by plan. Each query returns at most 2 K-lines. If more than 2 K-lines are requested, the system queries and returns 2.

4. Latest Trade Price Query Limits

  • /trade-tick: each query request can request the latest trade price for multiple product codes. The number of codes allowed per batch varies by plan.
  • If the request exceeds the number of codes allowed by the plan, the system only queries and returns results for the first codes within the allowed number.

5. Order Book Query Limits

  • /depth-tick: each query request can request order book data for multiple product codes. The number of codes allowed per batch varies by plan.
  • If the request exceeds the number of codes allowed by the plan, the system only queries and returns results for the first codes within the allowed number.

6. Static Information Query Limits

  • /static_info: each query request can request static information for multiple product codes. The number of codes allowed per batch varies by plan.
  • If the request exceeds the number of codes allowed by the plan, the system only queries and returns results for the first codes within the allowed number.

Notes

  • Plan your request strategy according to these limits to avoid unnecessary service interruptions.
  • These limits ensure fair service access for all users and protect backend systems from excessive load.
  • If you have questions or need further help, contact customer support.