Skip to main content

Sneak preview

· 4 min read

Take a look at our next software release and other upcoming features and improvements.

For the latest API updates, see our release notes or subscribe to our RSS feed.

What's in the next release?​

The next release is version 2.10.0. We expect this to include the following changes:

New​

Timestamps with nanosecond precision​

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

Request / MessageParameter name
Get server time REST and WebSockettimeNs
Create order response REST and WebSocketcreatedNs, updatedNs
Update order response REST and WebSocketcreatedNs, updatedNs
Get open orders response REST and WebSocketcreatedNs, updatedNs
Trades subscription trades eventtimestampNs
Track your orders fill eventtimestampNs
Track your orders order eventcreatedNs, updatedNs

After these parameters are live, we plan to deprecate the existing timestamps that use millisecond precision as part of a future release. 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 will 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: your limit, stopLoss, or takeProfit order has expired because there was no match, enough liquidity in the order book, or the timeInForce conditions have not been met. Your market order can also expire if you don't have enough balance on your account.
  • canceled: your order has been cancelled by either you or Bitvavo. You can find the cancellation reason under the returned restatementReason parameter implemented in v2.9.0.

What you need to do​

  • Update your integration to use the new nanosecond-precision timestamp parameters (*Ns). Plan to move away from using millisecond-based timestamp parameters in your systems.
  • Update your logic to handle the 200 OK response status code with "price": null and modify any logic that handles HTTP 500 for missing ticker prices.
  • Update your completed orders logic to be able to handle the new order status values and consume the cancellation reasons from the restatementReason parameter.

Coming soon​

In September 2025, we plan to release version 2.11.0. Besides other updates, this release will include:

Breaking change: Tick size validation​

Tick size is the smallest increment in the price of a crypto asset that you can change or quote on Bitvavo.

What is changing​

Depending on the market, we will determine the minimum price increment that can be made on Bitvavo. When the price is set, we will validate that the price is a multiple of the tick size. If it is not, we will return an error.

For example, if the tick size is 0.01, you will only be able to set the price to 1.00, 1.01, 1.02, and so on. If you try to set the price to 1.005, we will return an error.

Why is this beneficial​

This validation will help:

  • Keep the order book clean and consistent.
  • Setting precise prices for large orders or crypto assets like Bitcoin, which have a high tick size.
  • Minimize the risk of rapidly undercutting existing orders by the smallest possible amount.

What you need to do​

Make sure tha your app creates and updates orders with prices that are multiples of the tick size for the market you are trading on.

You can find the tick size for each market in the response to the Get markets REST or WebSocet request.