Release Notes

November 8, 2022

New Features

  • Support for stop orders

    With this release, we are glad to announce full support for stop orders, which further extends the range of trading options offered to B2BX clients. Both stop limit and stop market orders can now be configured, allowing you to postpone order activation until the market price meets the stop (or trigger) price specified for your orders.

    For stop buy orders, the stop price must be above the best ask price; for stop sell orders, the stop price must be below the best bid price (otherwise, the orders will be activated immediately).

    After the stop price is met and the order is activated, it becomes a regular limit or market order, which is then automatically placed on the order book or processed immediately according to the order time-in-force settings.

    Three new widgets have been added to the Trading Board to help you create and manage stop orders:

    • the Stop Limit and Stop Market widgets, which are used to configure and place stop orders according to your preferences

    • the Stop Orders widget, which is used to manage and monitor stop orders placed by you

    The Trading API has been updated as well by introducing new endpoints for managing stop orders:

February 10, 2022

  • Documentation UI has been upgraded.

  • Trading UI guide has been added. This guide is intended for traders, and contain the information on using trading interface as well as some tips on plotting chart and placing orders.

September 22, 2021

June 24, 2021

  • When subscribing to a WebSocket Channel, the complete current state is returned. All subsequent responses contain only updates, Summary.

  • Added update counter — version. On restart, the counter is reset. At the first snapshot, the counter is initialized and incremented on subsequent updates.

  • Added method GET frontoffice/api/orders?OrderId={orderId}, which returns information about the placed order. You can specify orderId (long) or clientOrderId (guid) in the query string parameters. If an order is received by clientOrderId, the current open order for this account is returned. If there is no open order, then the last order with clientOrderId for this account is returned. Note that method GET frontoffice/api/orders/{ClientOrderId} is now obsolete.

  • Changed responses for several methods:

    • executionPrice — new field, applicable for Market and Stop orders

    • requestedPrice — new field, applicable for Limit orders

    • price — obsolete field, for Market or Stop orders it is equal to executionPrice, for limit orders it is equal to requestedPrice. It is preferable to use executionPrice and requestedPrice instead of price.

    Full list of methods for which responses have been changed:

    • GET frontoffice/api/orders/{orderId}

    • GET frontoffice/api/orders/my

    • GET frontoffice/api/order_history

    • DELETE frontoffice/api/orders/{orderId}

    • DELETE frontoffice/api/{userId}/orders/{orderId}

    • POST frontoffice/api/order

    • Private WebSocket Method /ws/account. Channel name “OpenOrders”

April 22, 2021

  • Now you can get Get user balance for each asset.

  • We increased the security of the trading API (anti-replay protection). For Private REST Methods, the mechanism for signing requests will be changed. To ensure their integrity and authenticity, each request must include an arbitrary unique nonce, which will also be part of the signature. A transitional period will take 30 days. While transitioning, orders are accepted both with and without nonce. At the end of the transition period, processing requests without nonce will stop. The transition period ends on May 19, 2021.

November 17, 2020

November 2, 2020

October 7, 2020

September 11, 2020

  • The order can now be cancelled not only by orderId, but also by clientOrderId.