Hello @apollace,

Thanks for reporting it. We will take a look and get back to you.

Hello @carlosmiei, thanks, if you find anything I would be happy to see what was the issue in the PR 👍

@apollace Managed to reproduce the issue on my end, working on a fix right now.

@apollace can you please upgrade your ccxt version and try again? It should be working as expected now.

Thanks I will have a look this afternoon

Thanks for the fix, unluckily the client order id is not returned in the response in case of rejection. this makes the order stuck in case of rejection.

from the doc page (https://docs.bitvavo.com/#tag/Frequently-asked-questions/Trading):

Q: I've started working on connecting to Bitvavo and found out that rejection messages for the orders do not have any
information about which order was rejected. I subscribed for 'account' channel, and it doesn't have any rejection messages:

{
"action": "privateCreateOrder",
"market": "BTC-EUR",
"errorCode": 216,
"error": "You do not have sufficient balance to complete this operation."
}
There is no way to distinguish orders in WebSocket. Is it possible to add clientOrderId to rejection messages?

A: You can add a requestId to their request to trace the order.

In addition the version 4.4.29 broke the rest API

@apollace I will check this, I wasn't aware of the requestId, that would make things much easier.

In addition the version 4.4.29 broke the rest API

@apollace Can you elaborate a bit more here please?

@apollace I tried adding a requestId/id but as you can see the value is not returned

connecting to wss://ws.bitvavo.com/v2
2024-11-16T10:32:25.227Z onUpgrade
2024-11-16T10:32:25.228Z onOpen
2024-11-16T10:32:25.229Z sending {
  action: 'authenticate',
  key: '6ddbc7adbe112e98db39381e3358779ac735931e170acc65ac56f7d47daebd70',
  signature: '389a1022a455f9de9a44ba2b40c0dbe456e793da43e469eb185317464ca27fc1',
  timestamp: 1731753145027
}
2024-11-16T10:32:25.303Z onMessage { event: 'authenticate', authenticated: true }
2024-11-16T10:32:25.305Z sending {
  market: 'BTC-EUR',
  action: 'privateGetOrdersOpen',
  requestId: '17317531453043618'
}
2024-11-16T10:32:25.377Z onMessage { action: 'privateGetOrdersOpen', response: [] }
2024-11-16T10:32:25.379Z iteration 0 passed in 352 ms

[]

@apollace Oh Ok it needs to be an int:

nMessage { event: 'authenticate', authenticated: true }
2024-11-16T10:34:16.941Z sending {
  market: 'BTC-EUR',
  action: 'privateGetOrdersOpen',
  requestId: 17317532569411208
}
2024-11-16T10:34:17.021Z onMessage {
  action: 'privateGetOrdersOpen',
  requestId: '17317532569411208',
  response: []
}

@apollace Ok found the issue with the clientorderId as well, going to fix that too

@carlosmiei Sorry for the late response, I missed you comments.
I will test and let you know how it goes. Thanks for the help :)

I will ask to improve the doc because it doesn't look to be clear enough.

@apollace We haven't released yet, but we will do shortly

@apollace We just released a new version 4.4.32. Can you please upgrade and try again?

@carlosmiei Seems to work, I will let you know if I see more issues

@carlosmiei I can confirm that this issue is not present anymore. Thanks for the help!