What is an API request?


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

For TMY and Monthly Averages data products, one request is 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 your location, you will need two requests (1x location and 2x file formats) to get access to the data you require.

So the maths for figuring out how many API requests you need per month works out to be:

Locations * File Formats Per Location = API Requests Required

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

Helpful Tip - You can use our 'unmetered' locations while you practice using the historical data APIs. This means you can use as many requests as you need to get comfortable with using our APIs.

Did this answer your question?