The exact `last_price` submitted was not captured in our logs.
At the time of creation, the shares were not yet in holdings because their BUY GTTs had not triggered.
Could you please clarify:
1. Does Kite Connect API support MARKET orders in two-leg OCO GTTs? 2. Does the API support `market_protection` for GTT orders? If yes, what is the correct request field and accepted value? 3. Must the shares already be present in holdings before creating a SELL OCO GTT? 4. What are the possible causes of `Invalid trigger data` in this situation? 5. Is there any minimum required distance between `last_price` and the two trigger values?
The Kite web interface appears to support Market with Market Price Protection for GTTs. We would like to understand whether the same functionality is available through the API.