This is the v2 documentation and is no longer maintained. Please use the v3 documentation.
Skip to content

Request Sizing ​

Best Practices for request interval size and duration ​

Making large requests is often times inefficient and can lead to out of memory errors. Below we will go through the recommended date range limit for each type of resolution / asset class. Keeping responses to requests under 1 million ticks is the best practice. Going over the recommended date range may cause client or server side out of memory errors.

Asset ClassResolutionRecommended Date Range
StockTick-Level1-day
OptionTick-level1-week; 1-day for highly liquid tickers like AAPL / SPX / SPY
Any100ms1-week
Any1000ms1-month
AnyEOD1-month