Tick data enhancement - LTT to be in millisecond

vpr
Dear Team,

From the documentation https://kite.trade/docs/connect/v3/websocket/#quote-packet-structure, the LTT (Last Traded Timestamp) & ExchangeTimestamp that we receive is int32 (4 bytes) and cannot accommodate epoch in millisecond granularity. Once we receive multiple ticks for the same second, it becomes difficult to identify which tick got executed first (not able to determine order in the payload, i.e., is in sequence or jumbled). It becomes easy if we get the same in millisecond granularity.

BTW other providers like Upstox (https://upstox.com/developer/api-documentation/v3/get-market-data-feed) do provide the LTT in millisecond granularity and becomes easy to maintain the data in database or to perform any computation.

Looking forward to hear on this.
Sign In or Register to comment.