More changes in store for Saxo Bank’s OpenAPI in January

There are more planned changes in store for Saxo Bank’s OpenAPI. By early January 2019, the MarginImpactDetailed field group will be removed from the /trade/v2/orders/precheck endpoint.

Specifically:

• MarginImpactDetailed will no longer be a valid value for PreCheckOrderSpec.
• The MarginImpactDetailed field group will no longer be returned.

Developers are advised to use the MarginImpactBuySell field group instead.

Speaking of enhancements to the OpenAPI, let’s recall that FinanceFeeds has earlier reported that Saxo Bank is set to introduce a change this month whereby an order will retain the same order id, even if the order is filled over several exchange sessions. This change is poised to make it easier to keep track of an order and the position or positions created as the result of the order being filled.

Unless developers are keeping their own records between orders places and positions created, this change should not have any implications for them. In most situations they should not need to do this, as they should be able to trust that Saxo’s list of open orders (port/v1/orders) and positions (port/v1/positions) are consistent and correct.

If however, developers are keeping their own records, they may appreciate the improved ability to keep a connection between the order and the position(s) being created as a result of an order fill, even when the order fill happens over several exchange sessions.

Another benefit is the improved experience for a user, who will be looking at an open order showing the original order amount and the total filled amount, rather than a new order on a smaller amount.

The only potential impact could be if somehow developers’ application expects that two positions cannot have the same SourceOrderId.

Saxo Bank has been regularly updating its OpenAPI. In December 2018, FinanceFeeds reported about the addition of new authentication flows and a streaming solution to the OpenAPI.