Solcast Products

Evaluate Data Access

Data Modelling

Solcast API

Subscription Management

Hobbyists and Researchers

Troubleshooting and FAQs

Data Troubleshooting and FAQS

Third Party Integrations

User Guides

What you need to know when requesting data through the Solcast API

What does 'request' mean? How many requests does it take to get the data you need.

What is an API request?

If you've checked out our pricing page, or the Solcast API Toolkit, you'll have likely noticed we talk about 'requests' in reference to our historical data products.

For TMY data products, one request is equivalent to one file for one location.

How many requests do you need?

In order to determine how many requests you'll need, you may need to consider more than just the number of locations you need data for.

This is because each response formats (API speak for 'file format' or 'file type') count as their own request.

As a practical example - if you need both a CSV and a JSON file for one location, you will need two requests (1x location and 2x file formats) to get access to the data you require.

To figure out how many API requests you need for a month, you can use the computation below:

Locations * File formats per location = API requests required

Read more about our response format options in the API Toolkit or in the docs.

On this page

• What you need to know when requesting data through the Solcast API
• What is an API request?
• How many requests do you need?