Trailing Stop Error

0xBreath · May 14, 2023, 10:24pm

Trying to place an order to the test network via the api/v3/order Spot API endpoint with a trailingDelta.
I have tried LIMIT, STOP_LOSS_LIMIT, TAKE_PROFIT_LIMIT order types with the trailingDelta optional field, but it throws the error missing field price or missing field symbol.

The order definitely has these fields, the exchange info endpoint api/v3/exchangeInfo for Spot BTCBUSD or BTCUSDT says that the order types I tried are valid: LIMIT, STOP_LOSS_LIMIT, TAKE_PROFIT_LIMIT.

And the endpoint api/v3/account says that I have permission to trade SPOT for the test network.

The documentation for Spot API says that trailingDelta is supported for these order types.

Here is one of the requests that throws the error "missing field price", line: 1, column: 125

https://testnet.binance.vision/api/v3/order?symbol=BTCBUSD&side=BUY&type=TAKE_PROFIT_LIMIT&timeInForce=GTC&quantity=0.00828&price=26907.21&trailingDelta=95&timestamp=<timestamp>&signature=<signature>

I am referencing this Spot API documentation:
https://binance-docs.github.io/apidocs/spot/en/#new-order-trade

and this GitHub Trailing Spot FAQ documentation, which I have replicated but still throws the error shown above:

github.com

binance-us/binance-us-api-docs/blob/master/faqs/trailing-stop-faq.md

# Trailing Stop order FAQ

## What is a trailing stop order?

Trailing stop is a type of contingent order with a dynamic trigger price influenced by price changes in the market. In the API, the change required to trigger order entry is specified in the `trailingDelta` parameter, and is defined in BIPS.

Intuitively, trailing stop orders allow unlimited price movement in a direction that is beneficial for the order, and limited movement in a detrimental direction.

Buy orders: _low_ prices are good. Unlimited price _decreases_ are allowed but the order will trigger after a price _increase_ of the supplied delta, relative to the _lowest_ trade price since submission.

Sell orders: _high_ prices are good. Unlimited price _increases_ are allowed but the order will trigger after a price _decrease_ of the supplied delta, relative to the _highest_ trade price since submission.

## What are BIPs?

Basis Points, also known as BIP or BIPS, are used to indicate a percentage change.

BIPS conversion reference:

BIPS | Percentage | Multiplier
---- | ---------- | ----------

This file has been truncated. show original

aisling2 · May 15, 2023, 2:25am

Maybe it’s related with how your local code is sending the request?
Because I’ve tried:
POST https://testnet.binance.vision/api/v3/order?symbol=BTCBUSD&side=BUY&type=TAKE_PROFIT_LIMIT&timeInForce=GTC&quantity=0.00828&price=26907.21&trailingDelta=95&timestamp=<timestamp>&signature=<signature>

Using Binance API Postman and was able to get response:

{
    "symbol": "BTCBUSD",
    "orderId": 3712123,
    "orderListId": -1,
    "clientOrderId": "lfpMbxmzKshMfU5AcIwG7Q",
    "transactTime": 1684117386391
}

0xBreath · May 20, 2023, 6:26pm

Thanks for the quick reply! Yes, you’re correct. I got it to work with Postman as well.
My issue was the JSON response for different Orders varies.
I was deserializing the Order response into a struct with a field ‘price’ that did not exist on the response I was actually getting:

{
    "symbol": "BTCBUSD",
    "orderId": 3712123,
    "orderListId": -1,
    "clientOrderId": "lfpMbxmzKshMfU5AcIwG7Q",
    "transactTime": 1684117386391
}

Nothing to do with Binance API. It was a deserialization bug (I’m in Rust).