timestamp column in KiteConnect 3.0 doesn't have milliseconds?

sidverm

Hello all,

I am using KiteConnect 3.0 Python API. There is a timestamp column that comes in the ticks. On printing it is displayed only upto second (not milliseconds). Is it true?

Regards,
Siddharth

sujith

We get Unix timestamp (seconds) from the exchange. We just pass it to the client.

sidverm

Oh, on colo the exchange does provide timestamp upto millisecond accuracy, I am pretty sure about it. I have sample co-lo data for a day, it clearly has millisecond time-stamp. In fact, my most read post on this forum, that quantified delays in zerodha streaming data, was calculated using unix time stamps from exchange that I got from a friend for a day.

How is it that exchange provides zerodha only upto a second, and others millisecond data?

sujith

We don't get TBT data. All the members get only level 2 data and that doesn't have milliseconds timestamp.