The order history data is synchronous. Only the websocket event is async in nature. There can be many entries. It does cover all state transitions. If you just need the latest status of an order, an orderbook API call is enough though. You may use order update as an event to fetch orderbook.
For postbacks, you will only get order updates for orders that are only placed from your app and not from Kite web or app. Whereas on websocket API you will receive order updates for all the orders. Websockets order updates are better than postbacks for individual users.
Ok .I was trying to compare relying on WS updates vs kite.orders(). What do u think ? i feel ws update will be faster and api call will be an overhead.
There can be many entries. It does cover all state transitions.
If you just need the latest status of an order, an orderbook API call is enough though. You may use order update as an event to fetch orderbook.
What is the downside of relying only on WS updates (given that i have uninterrupted broadband connection/aws setup) ?