By algo bot is not placing stop loss and target when the order is getting deployed

I'm building an automated trading system on the v3 API and need clarification on two chart-rendering behaviours that are causing operational confusion.

1. Both SL-Market and Limit Sell orders display as "Sell StopLimit" on the chart

When I place a protective bracket on an option position consisting of:

  • One type=3 SL-Market order (stopPrice set, limitPrice=0, side=-1)

  • One type=1 Limit Sell order (limitPrice set, stopPrice=0, side=-1)

the Fyers chart UI labels both of them as "Sell StopLimit". This is misleading — the type=1 should display as "Sell Limit" since it has no stop trigger, only a limit price. Visually distinguishing SL-Market and Limit Sell orders on the chart is critical for an operator monitoring positions live. Could you confirm whether this is intended behaviour, and if so what label distinguishes the two on the chart?

2. Limit Sell (type=1) target order at a price ABOVE current does not appear visibly differentiated

Related to the above — when I place a Limit Sell at a price above current LTP (intended as a profit target on a long option position), the chart shows it with the same "Sell StopLimit" tag as my SL-Market on the same symbol, which makes it impossible to tell the SL apart from the Target visually.

3. Confirmation requests:

  • Please confirm the exact type integer codes returned by the orderbook endpoint (1=Limit, 2=Market, 3=SL-Market, 4=SL-Limit) so I can map them in my UI.

  • Please confirm the full list of status codes returned by orderbook (specifically: 1=Cancelled, 2=Filled, 4=Transit, 5=Rejected, 6=Pending, 7=Expired — is this complete?).

  • Is there a chart-side option or API flag that forces distinct rendering for type=1 (Limit) vs type=3/4 (SL/SL-Limit)?

Account: XR*****
SDK: fyers-apiv3 (Python)

Thanks,
ROHIT MODAK

Also i want to ask Hi, I'm using fyers-apiv3==3.1.12 with v3 REST. When I send productType:"BO" in place_order for an NSE option, I get error -50: productType must be one of: CNC, MARGIN, INTRADAY. Is BO supported via API for F&O options today? If yes, please share an exact working payload with the correct productType value. If no, what's the official ETA?

3 replies