Sneak preview
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?
We plan to release two versions in September 2025. We expect these to be:
v2.11.0
New
Cancel on disconnect
In case of network disconnections, extreme latency, or similar issues your orders can remain open and be filled at unfavorable prices while you are disconnected.
To prevent this, we will introduce a new optional feature, Cancel on disconnect. This will automatically cancel your open orders if there is no activity from you for a set period of time.
We will soon share more details about how to enable and use this feature.
Timestamps with nanosecond precision
For the following requests, we will add new timestamp parameters with nanosecond precision:
| Request / Message | Parameter name |
|---|---|
| Get order response REST and WebSocket | createdNs, updatedNs |
| Get orders response REST and WebSocket | createdNs, updatedNs |
v2.12.0
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
For every 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 that your app creates and updates orders with prices that are multiples of the tick size for the market you are trading on. To prepare for this change, use this document to get the tick size values on the day of release.
After the release, we will periodically recalculate the tick size for each market based on the market conditions. To get the tick size, you can make Get markets REST or WebSocket requests.
Deprecated
pricePrecision
As we will introduce the tick size validation, the pricePrecision response parameter to the Get markets REST and WebSocket requests will now always return the value null. We will remove this parameter in one of the next releases.