Hello, What syntax do you use to place orders on Bingx? I’ve been trying everything possible for hours, but nothing helps, I get FAILED messages in return.
Hello @Gonzo
It would have been better to share the commands that you have tried as per this BingX Automation Guide
I would also like to know the response you get when you click Send a Test so that we can know if the issue is with the Webhook configuration.
Tash
Here are the errors
(Send in Test Mode)
Your notice “Alerts To Bingx” is not very explanatory on the possibility of orders
BingX has 3 ticker
(BTCUSDT) for spot => C=SPOT
(BTCUSDT. P) for Perpetual => C=FUTURES
(BTCUSDT. PS) for Perpetual Std. =>?
How to use Perpetual Standard?
I don’t see anything to include SL and TP or Trailing Stop in the purchase order
Thanks for your help
Thank you.
The commands fail because the Position Mode Settings in BingX are set to Hedge Mode.
The are two solutions to this:
- Use the Hedge parameter at the end of your commands. For example,
Buy BTC/USDT C=FUTURES HEDGEor - Change the Position Mode settings to one-way in BingX
Standard Futures are not supported by API trading, so only the USDM and COINM Perpetual Futures are supported.
Okay, thank you, it works now.
3 lines to directly add SL and TP
LONG BTC/USDT L=1 Q=25% C=FUTURES HEDGE
LONG BTC/USDT SL =5% C=FUTURES HEDGE
LONG BTC/USDT TP=5% C=FUTURES HEDGE
I just have one more problem for closing orders
CLOSE BTC/USDT…
(Close all order, long & short)
How to close only a long or shorts?
CLOSE LONG or CLOSE SHORT are not accepted
Do you have a list of functions and possibilities, because the Bingx page is incomplete and wrong, the error with HEDGE I made it because on the page it talks about Binance where is described “HEDGE”.
No description for TP and SL
I tested it myself, and it worked.
But it wouldn’t be a luxury to have a page with all the functions currently supported .
It would avoid unnecessary waste of time
Although it works, there are still points to clarify.
I have problems with the quantities “Q”
The percentage does not represent the value of the usable funds
And if I put Q in quantity, I have random errors
Example:
LONG TUT/USDT L=2 Q=692.2810661128 C=FUTURES HEDGE
LONG TUT/USDT SL =3% C=FUTURES HEDGE
LONG TUT/USDT TP=10% C=FUTURES HEDGE
Result:
Failed
Order Sent and Opened!
ExchangeError bingx {“code”:110424,“msg”: “The order size must be less than the available amount of 1384.4 TUT,”"data:{}} Quantity: 3418.88080804
(The order opens but no TP or SL is placed)
Example 2: (same Alert Command)
SHORT LUCE/USDT L=2 Q=1597.4440894569 C=FUTURES HEDGE
SHORT LUCE/USDT SL =3% C=FUTURES HEDGE
SHORT LUCE/USDT TP=10% C=FUTURES
Hedge
Result:
Order Sent and Opened!
Order Sent and Opened!
Order Sent and Opened!
Another problem, the lever is not always respected, it happens that the lever previously set to Bingx takes the place of the lever “L=…”
Under his conditions it becomes complicated and dangerous to leave the script unattended.
Hello Gonzo,
In our BingX Automation Guide, there is no TP/SL mention.
This is because TP/SL is currently not supported for BingX.
Q is a percentage of your Equity, not the Account Balance.
I have asked the developers to look at the leverage issue as I have noted a similar issue and update us as soon as possible.