FAQ: Error message "Order does not exist" says that /api/v3/order can return stale data because it uses a “persistence layer” which may not know about all of the events that have gone through the matching engine.
Does /api/v3/account use the persistence layer (which may be delayed) or the information used by the matching engine? (The matching engine must have up to date account info to avoid letting me sell assets twice and to let me sell assets that I just bought.)
Please use wss user data stream if you want instant update
The user data stream is event-driven but it is not “instant;” it lags reality when it matters most.
Can I get an answer to my question instead of a discussion of alternatives?
Matching engine has the account’s latest balance, no one can over spend any asset. So yes this endpoint is up to date.
Just to confirm - you (Dino) are saying that “/api/v3/account” always has the latest balance, the balance that will be used by the matching engine.
I call /api/v3/account when I know that I have no outstanding orders and want to rely on what it returns to create new orders.
Thanks.