@PJ_2018 Although, the ws.close and ws.stop are commented out in the above code but if they are used inside on_close, would it stop websocket from trying to reconnect.

this might help.

@ZI4453

@healthsecure15

@rishiswethan @jeevansevar

The pykiteconnect documentation does not state anything clearly - I looked at https://kite.trade/docs/pykiteconnect/v3/#kiteconnect.KiteConnect.orders

@ZI4453

for modification go through this link: https://kite.trade/docs/pykiteconnect/v3/#kiteconnect.KiteConnect.modify_order

have a look to this link : https://kite.trade/docs/pykiteconnect/v3/#kiteconnect.KiteConnect.margins

to fetch historical data go through this link : https://kite.trade/docs/pykiteconnect/v3/#kiteconnect.KiteConnect.historical_data

https://kite.trade/docs/pykiteconnect/v3/#kiteconnect.KiteConnect.margins

https://kite.trade/docs/pykiteconnect/v3/#kiteconnect.KiteConnect.historical_data

@gagneetkalsi

@tradeWise,

https://kite.trade/docs/pykiteconnect/#kiteconnect.KiteConnect.invalidate_token

Refer: https://kite.trade/docs/pykiteconnect/v3/#kiteconnect.KiteConnect.cancel_order

Closing an MIS involves only placing an order of opposite transaction type. But to close a cover order position, one has to modify the second leg order to market type. This is taken care of by the sy…

You can check out the pykiteconnect documentation here for more information regarding the on_order_update callback.

@AnujaJ

I was not able to find a proper documentation on various parameter values of the order_place() API. Some of the order information is available at the Kite User Manual.