Skip to main content

Bitvavo Trade Connector

Features​

crypto-bitvavoConnector Key
Instruments
FX
Request Types
SUBMITCANCELREPLACE
Order Types
MARKETLIMIT
Time In Force
GTCIOCFOK
Order ID Mapper
SEQUENCE
✗
Order Status Request
✗
Cancel On Disconnect
✓
Commission
✓
Post Only
✓
Fast Cancel
✗
Fast Replace

Notes​

tip

Please consider switching to Bitvavo FIX Trade Connector.
Institutional traders and market makers can use it for high-volume, low-latency order execution.

Location​

Bitvavo is hosted in the Amazon Frankfurt region.

Operator ID​

Operator ID is an integer that you specify to identify the trader or algorithm responsible for each order submitted using your API integration.
It enables clearer attribution of trading activity, which is critical for compliance and auditability.

note

If the operatorId config parameter is not set, the connector uses the absolute value of the order request's SourceID in Alphanumeric encoding.

Subscription​

The connector subscribes to all instruments at once. Bitvavo rejects the subscription if one or more symbols are invalid, causing the connector to drop and re-establish the connection.

Order Replacement​

What happens during the update is that the order is taken out of the order book, during the update, and then placed back. However, if the user places an order, but while being processed on the API, that order is matched and filled on the ME, that order will already be marked as filled.

note

The effective open quantity during replacement should exceed minimal order quantity.
I.e. Replacement Qty - Filled Qty >= Min Order Qty

Rate Limits​

Each REST endpoint and WebSocket action in Bitvavo API is allocated Rate limit weight points.

Symbology​

https://api.bitvavo.com/v2/markets

Configuration​

Connector settings​

ParameterDefault ValueDescription
selfMatchPreventionInstructionCANCEL_TAKINGSelf-Match Prevention Mode. Allowed values: CANCEL_TAKING, CANCEL_RESTING, CANCEL_BOTH.
operatorIdOperator ID is an integer that you specify to identify the trader or algorithm responsible for each order submitted using your API integration. It enables clearer attribution of trading activity, which is critical for compliance and auditability.
clientTerm0The constant value for MSB (most significant bits) in client order id UUID.

Supported order attributes​

KeyDescription
186 value used for Post Only orders submission.

Config sample​

connectors {
BITVAVO: ${template.connector.crypto.bitvavo} {
settings {
restUrl = "https://api.bitvavo.com"
websocketUrl = "wss://ws.bitvavo.com/v2"

apiKeys = [
{
apiKey = "<API_KEY>"
apiSecret = "<API_SECRET>"
}
]
}
}
}