v2.10.0

New

Timestamps with nanosecond precision

For the following requests, we added new timestamp parameters with nanosecond precision:

Request / Message	Parameter name
Get server time REST and WebSocket	timeNs
Create order response REST and WebSocket	createdNs, updatedNs
Update order response REST and WebSocket	createdNs, updatedNs
Get open orders response REST and WebSocket	createdNs, updatedNs
Trades subscription trades event	timestampNs
Track your orders fill event	timestampNs
Track your orders order event	createdNs, updatedNs

In a future release, when all users have switched to using nanosecond precision, we will deprecate the existing timestamps that use millisecond precision. We will announce this in advance, so you can prepare for it.

Changed

Get ticker price

For the Get ticker price REST and WebSocket requests, when there is no price available, we now return HTTP 200 response with "price": null instead of an HTTP 500 error.

Completed orders status changes

In the lifecycle of an order, completed orders can now only have the following statuses:

• filled: all trades necessary to complete the order have been filled.
• expired: the order never gets added to the order book because there is no match, enough liquidity in the order book, or enough balance in your account. Also, if you set the timeInForce parameter to IOC or FOK for your order, the order can expire if those conditions are not met.
• canceled: the orderId is removed from the order book by either you or Bitvavo.

We now return the specific reasons for cancellation using the restatementReason response parameter. To learn more, see Canceled orders.