Kindly check if dotnet api suupports decimal value in BO orders for Tr SL and SL. I am giving trailing SL,SL more than 1 rs suppose 1.3 Rs it is giving error . SL price should be multiple of 0.05
@Kanchana,
It does accept decimal values, but minimum value for trailing stop-loss is 1.
Values for square off, stop-loss and trailing stop-loss has to be in points and must modulus of tick size.
@sujith, Please also let me know why the minimum value for TSL is 1. There are so many scrips which move only by 5paise. In those cases, a minimum TSL of Rs1 would be disastrous. Let me know if you think otherwise.
@sujith Thanks for the reply. I understand that this is to avoid load on servers, but again, can you please confirm the trailing stop loss is always 'absolute' value. I tried a TSL of 1.1 on SHRIRAMCIT, it failed stating that the tick size should be multiple of 0.05. The help tip of Trailing Stoploss popup window for a BO order says 'Absolute value, min 0.05 for CDS 1 for all others'. In PI window TSL is always on Ticks. I think there is some confusion here. Please clarify.
@Kanchana, The minimum value for trailing stop-loss is 0.05 for CDS segment and 1 for other segments. Kite Connect always accepts values in points. It doesn't support tick values for trailing stop-loss, stop-loss and target values.
We have informed the OMS team regarding the modulus issue of trailing stop-loss, they are looking into this.
Can you let us know tradingsymbol and exchange?
Seems like the issue from OMS side validation. We have informed concerned team.
I am not sure because it is from OMS vendor. I will update once it is fixed.
It does accept decimal values, but minimum value for trailing stop-loss is 1.
Values for square off, stop-loss and trailing stop-loss has to be in points and must modulus of tick size.
You can check out this thread.
The minimum value for trailing stop-loss is 0.05 for CDS segment and 1 for other segments.
Kite Connect always accepts values in points. It doesn't support tick values for trailing stop-loss, stop-loss and target values.
We have informed the OMS team regarding the modulus issue of trailing stop-loss, they are looking into this.