Skip to main content

Fair use policy

You can notice when working with the API that the resources available to the user have quite few restrictions and prohibitions. This is done in order to make interaction with the trading system more convenient.

Nevertheless, when providing access to the API, we expect users to be guided in their actions by the fair use concept.

Our vision of the fair use concept means interaction with the API of the system, in which user's actions do not affect the performance of the system in general and the stability of its operation for other clients in particular. Unfair use on the other hand is any action, including unintentional, that can negatively affect the system functioning.

Examples of Unfair Use​

Unfair use of the system includes, but is not limited to:

  • Frequent (multiple times per second) sending of requests to create Access tokens for each individual API request
  • Frequent (several times per second) execution of big data requests
  • Frequent (several times per second) execution of duplicate requests of the same type
  • Transmission of obviously meaningless data to the system or messages with incorrect syntax causing errors in processing of received requests
  • Supporting multiple unused WebSocket connections or raising and closing a connection for each separate request And other actions that may cause unreasonably high consumption of system resources
caution

In case of detecting signs of unfair use, the Broker has the right to temporarily suspend the processing of requests from the user committing objectionable actions until the circumstances are clarified and the reasons for such actions are eliminated.

Examples of Fair Use​

The following are recommendations for fair use of the system:

  • Use one or more Access tokens for all requests sent, updating them at 15-20 minute intervals. The lifetime of Access token is 30 minutes, refreshing it every 20 minutes will prevent the request denial due to expired token lifetime
  • If the data is static (list of exchange instruments, transaction history, etc.), update the data every few minutes or use WebSocket subscriptions to get up-to-date data when it changes
  • Ensure that the information being transmitted is correct by testing your software on the Test Environment
  • Limit the number of simultaneous WebSocket connections to reasonable limits. We recommend using 1 connection for order management requests and up to 10 connections for managing information subscriptions

What's next?​

Additionally, we recommend reading the following related articles:

By using the resources (documented and not) provided by the system, you accept the Platform Rules that are in force at the time you execute the request.