the product type received from kite.history() API call is same. It should be converted into new product type. Also, it is not refreshed into the orderbook.

You will have to listen to order updates on the websocket API. You can know more here.

https://kite.trade/docs/connect/v3/postbacks/#payload-attributes

In the meantime, there can be many use cases that can use the postback url.

https://kite.trade/docs/connect/v3/orders/#placing-orders

https://kite.trade/docs/connect/v3/portfolio/#positions

how do I handle conflicting exits on the same instrument

If you need to keep a track of m2m/P&L, you can refer to positions m2m https://kite.trade/docs/connect/v3/portfolio/#positions

https://kite.trade/docs/connect/v3/portfolio/#positions

https://kite.trade/docs/connect/v3/portfolio/#positions

(A) Place entry order (LMT) - https://kite.trade/docs/connect/v3/orders/#placing-orders

##pass

https://kite.trade/docs/connect/v3/portfolio/#positions

https://kite.trade/docs/connect/v3/postbacks/#postback-webhooks

Am I missing something? One can try with this code after the kws.connect(threaded=True). On my system in 10 secs about 25000 (25k) twenty five thousand while_ticks functions were created. # Infinite

You can refer to the FAQs here.

1 ) While placing GTT Orders via api can you support "TAG" attribute , like it is supported in normal orders it will be helpful to map GTT updates

https://kite.trade/docs/connect/v3/postbacks/#postback-webhooks

And is there any example of zerodha order creation using nodejs anywhere? I checked the documentation https://kite.trade/docs/kiteconnectjs/v3/KiteConnect.html#placeOrder

#python #tradecopy #api #developer #tool #algo #copier #copytrading