0
Follow
0
Followers
L'API OKEX V5 utilise exchange.IO("api", "POST", "/api/v5/trade/cancel-algos", params) et continue de signaler une erreur Futures_OP 4 : 400 : {"code : "50000", "data" :[],"msg":"Body can not be empty...
Created 2021-10-15 11:39:26
2
1271
Par exemple: OKEX V5 api utilisée par exchange.IO ((( "api", "POST", "/api/v5/trade/cancel-algos", params) a toujours manqué Futures_OP 4: 400: {"code":"50000","data":[],"msg":"Body can not be empty."}
paramètre:
var params = {
"instId":"CVC-USDT-SWAP",
"tdMode":"cross",
"side":"buy",
"ordType":"conditional",
"sz":"1",
"slTriggerPx":"0.55",
"slOrdPx":"0.55"
}
var ret = exchange.IO("api", "POST", "/api/v5/trade/cancel-algos", params)
Retour à zéro
Il y a aussi un article sur le site de l'association "Futures_OP 4: 400".[],"msg":"Body can not be empty."}
Je ne sais pas si vous pouvez m'aider, mais je pense que c'est un problème de gorge.
Related Recommendations
How to Specify Different Versions of Data for the Rented Strategy by Its Rental Code MetadataAdvanced Tutorial for FMZ Quant platform Strategy WritingElementary Tutorial for FMZ Quant platform Strategy WritingGet Started with FMZ Quant PlatformSECURITY BUGI keep getting error: Exchange_GetAccount: Invalid ContractTypeWe have an incredibly profitable market making algorithm for sideways markets on Bitmex - but need expert to help eliminate wait times during downward volatility in the marketError with deribitLimitations of the backtesting engineHow to install ta-lib on linux docker?
