>>8631159
Not a websocket endpoint, if we're trying to make sheets not run out of control, the solution would have to be something the sheets can easily implement.
>>8630984
You're still free to call the regular getuserinfo endpoint to fetch your wallet before you make your decision, just fetch it once, decide the actions you want to take, pack it all into a lis, send it as a batch and receive the result in 1 http request
Of course you can follow up on the response, but I think basic traders will just wait 10 minutes at this point.
Side note:
Right now even if I fetch the wallet once, every coin I have to trade has to individually be sent as a separate http req, with 1 websocket acknowledgement and confirmation.
The only optimization is to reuse the same http session, and I'm unsure if sheets do that.
The main problem is still scripts going wrong and spiralling out of control though. Hence my suggestion to run one function every 10mins, less ways to screw that up without having to track every coin individually.
Not intending to sound disparaging, but its essentially a separate simplified api so its easier to write scripts/sheets that don't fuck up.