Protective block
Moscow Exchange takes the right to act against traders who massively send non-executable requests to manage (place, modify, withdraw) orders: from charging an additional fee to temporary login blocking. More details about non-executable requests and possible consequences of sending them can be found in Exchange documentation.
To avoid such consequences for our users, we have added our own mechanism of automatic user blocking, giving API users the opportunity to quickly fix errors in requests they send without drawing the exchange's attention.
Features
The automatic blocking mechanism has some specific features, which should be noted:
- Works only for the derivatives market. Errors in other market sectors are not covered by the mechanism.
- Errors of each type are counted separately. Each type of errors has its own counter. The counters of different error types are not summarized - blocking by one error type will take the need to reach its limit.
- The block will be removed automatically. User will be unblocked automatically after the period specified in table below. Manual and early unblocking options are not available.
- Unblocking clears the error counter. Only the error type that caused the blockage will be cleared. Other counters will keep the values obtained before the blockage.
- Resetting counters does not affect the Exchange. The exchange continues its own counting regardless of the protective blocking mechanism. If the system blocks a login for the third time in a row because of the
Order not founderror, you can have no doubt that the Exchange has recorded at least 1200 errors of this type. - The mechanism has a 60-second cooldown period. Once the previous blockage is removed, the system will start counting new errors, but will not take any action against the user during the first 60 seconds.
Blocking and unblocking
The automatic blocking mechanism monitors the following types of errors that will result in a user being blocked if spammed:
| Error type | Limit | Blocking time, sec. |
|---|---|---|
Trading session suspended or closed | 400 | 1800 |
Security not found | 400 | 1800 |
Unspecified (or unknown) error from exchange | 2000 | 1800 |
Cross deal occurred | 400 | 1800 |
Insufficient client funds | 400 | 1800 |
Insufficient brokerage firm funds | 400 | 1800 |
FOK order not reconciled | 400 | 1800 |
Order not found | 400 | 1800 |
The Transaction completed successfully and no orders (0) deleted error type is not currently tracked by the mechanism. Be careful when sending a request to cancel all orders.
What's next?
The mechanism described above provides protection of the user from sanctions from the exchange. In addition to it, there are also mechanisms to protect the system from user actions. To avoid them, check the platform Terms of Service and our meaning of the API fair-use concept.