rajiv

I suspect it is ordered lexically by `id`, which is only approximately chronological. PS--At one time the `id`s were discontinuous at 1pm Eastern each day. Hopefully _that_ has been fixed.

> the code to figure out if a trade with some timestamp happened pre-market or during regular market hours is surprisingly non-trivial Wouldn't the trade condition indicate (more accurately) whether...

JSON does not "convert" anything, it's just a data format. Large, high-resolution numbers are totally valid JSON, but your language and/or parser may have limitations. I use Javascript, and it...

> the full timestamp is used as a paging cursor Yes 😞 , yes it is. My code works around that by counting how many records were in the last...

> 64bit integer types Surely you mean 64-bit _floating point_ types?

@kmcminn I'm not sure I know what you're saying. That number would easily fit in a 64-bit int, which Javascript doesn't have.

@kmcminn , I feel like you're on a tangent. That doesn't test anything about JSON deserialization, but rather your language and whatever datatype you're using. @tr8dr is suggesting quoting the...

I currently use Alpaca's [calendar endpoint](https://alpaca.markets/docs/api-documentation/api-v2/calendar/) for this data.

This split for TQQQ says 2017-01-11, but it actually happened on 2017-01-12 

Empty results are the right response for _valid tickers_ during _time periods in which no quotes occurred_. This would include weekends, holidays, overnight, maybe even trading halts. However, for genuinely...