Release notes
v2.6.0 - 2025-02-06
New
- For HTTP 400: Bad Request, we now return an error code 429 when a parameter value has too many decimal places. The number of decimal places can vary per market.
- For HTTP 503: Service Unavailable, we now return error codes:
- 430 when a connection times out because no new market data events are received.
- 431 when we cannot retrieve data for a market because it isn't in a trading status.
Changed
- When making an Update order request, the
fills
object in the response now only includes the fills generated by the request instead of all historical fills for the specifiedorderId
. - In the Create Order request, Update Order, and Cancel Order requests, the
clientOrderId
must only have a unique identifier among the open orders of that user. When the orders are closed, you can reuse thatclientOrderId
. - Specifying the
clientOrderId
query parameter in the Get order request now only returns the latest order for thatclientOrderId
. - When making a Get orders request, the value of the
clientOrderId
is only returned for the latest order of the sameclientOrderId
. The values for earlier orders that used thatclientOrderId
isnull
. - The Get balance request now only returns the assets that have a balance greater than 0.
- When retrieving the order book or subscribing to ticker and book endpoints, the data is now only returned for the markets that are in a trading
status
. - When making a Get order book request, the maximum
depth
of bids and asks to retrieve in a single request is now 1000.
Deprecated
- The Get open orders request now returns an empty
fills
object instead of all historical fills for the specifiedorderId
. This parameter will be removed in the next version. - When creating a new order, setting the
disableMarketProtection
parameter no longer works. If included, the request does not fail, but it ignores the parameter.
v2.5.0
New
- We have added a new Transaction History endpoint to retrieve the transaction history of your account. You can filter transactions by type and date range.
v2.4.0
New
- We have added a new Fees endpoint to retrieve the transaction costs you are charged for trading in a specific market.
v2.3.0
Changed
- We improved tracking of order status with the
clientOrderID
parameter:- Update and Cancel orders now have a unique
clientOrderId
. You can set this ID for every Create order. clientOrderId
is returned in the response for the Trading subscription WebSocket.
- Update and Cancel orders now have a unique
v2.2.2
Changed
We updated the Rate limits policies.
v2.2.1:
New
- You can now set a unique clientOrderId for every new order. You use this ID to easily track the order status.
- You can set a unique requestId to an initial WebSocket request. This value is added to the return parameters for the action.
v2.2.0:
New
- We added
stopLoss
,stopLossLimit
,takeProfit
, andtakeProfitLimit
order types. - We added the Account endpoints.
v2.1.2:
New
- We added networks to assets.
v2.1.1:
New
- Added orderId to user trades.
v2.1.0:
New
- Added
bestBidSize
andbestAskSize
to thetickerBook
and the WebSocket ticker. - Added
bestBid
,bestBidSize
,bestAsk
,bestAskSize
, andtimestamp
parameters toticker24h
. - Added the
tradeIdFrom
,tradeIdTo
,orderIdFrom
, andorderIdTo
parameters to limit returned trades and orders (deprecatingtradeId
orderId
in those searches). - Added a
ticker24h
WebSocket stream.