Bulk historical data retrieval is a common use case for many of our users. We have some recommended practices for using the API do retrieve large amounts of historical data.

  • For the best performance when retrieving a large amount of data for many locations: Break up any large request into smaller parts. For example, instead of retrieving one year of data per request - retrieve only 1 month per request.
  • In general, our historical data servers are better optimized to handle many small requests, rather than singular large requests. Smaller concurrent requests are preferred to fewer large requests. However, keep in mind the req/second limitations of your subscription.
  • Add http request retry logic to any long-running script. Preferably with an exponential backoff algorithm.
  • Alternatively, use the Historical Data Custom Order System in the dashboard (note: this service is invoiced separately).