What is a Time Series data 'request'? How many 'requests' do I need?

What is a Time Series data 'request'? How many 'requests' do I need?

Solcast Products

Live and Forecast
Grid Aggregations
Typical Meteorological Year (TMY)
Geographic Horizon Angles


Modelling - FAQsModelling - FAQs
Explaining Terms

Solcast API

Third Party Applications

Hobbyists and Researchers

Home Hobbyist Accounts
Researchers and Academic Accounts

Troubleshooting and FAQs

FAQsFAQsTroubleshooting Data ErrorsTroubleshooting Data Errors

Useful Links

Postman API (Spec) Documentation

Python SDK

API Change LogAPI Change LogSubscription ManagementSubscription ManagementAccount FAQs

How many requests do you need?

Discover how you can calculate the number of Time Series data requests you need for your data requirements.

What is a Time Series data request?

If you've checked out our pricing page, or the Time Series data ordering tool in the Solcast API Toolkit, you'll notice that we talk about 'requests' in reference to our Time Series data product.

In the simplest of terms, one request = up to 31 days of Time Series data for one location.

However, in order to determine the number of requests required, you’ll need more than just the number of locations and years.

How many requests will you need?

Each of our response formats (also known as 'file format' or ‘file type’) count as their own request.

This means that aside from the number of location and months, you also need to consider the time granularity of the data you require as well as the number of file format.

For example, if you need both a Solcast CSV and a PVsyst file for one year of data from your location, you will need 24 requests (1x location * 2x file formats * 12x months).

To sum it up, here’s how you should compute for the number of requests you need:

Locations * Number of Months * File Format = API Requests Required