Choose an API Plan for Instant Access to the Degree Days.net API

The Degree Days.net API (Application Programming Interface) will give your software automated access to data from our service, including data going further back in time than our free website allows.

Choose one of the 8 API plans below to get your API access keys immediately after signup. You can enter your API access keys into compatible software (like our desktop app) to enable it to automatically fetch degree days on your behalf. Or you can use your API access keys to build degree days into your internally-developed software systems.

The rate-limited API plans offer the most flexibility and are the best choice for most customers. The higher the hourly rate limit (request units per hour*), the more data your software can fetch from the API in any given hour:

API Premium	API Plus	API Standard	API Basic
$1,995/month	$695/month	$195/month	$49/month
Up to 12,000 request units per hour^*	Up to 4,000 request units per hour^*	Up to 1,000 request units per hour^*	Up to 100 request units per hour^*
Degree days^†	Degree days^†	Degree days^†	Degree days^†
Hourly temperature data^‡	Hourly temperature data^‡	Hourly temperature data^‡
Regression^§	Regression^§	Regression^§
Pro website access^‖	Pro website access^‖	Pro website access^‖
Priority support^¶	Priority support^¶
Our highest rate limit for customers needing large quantities of data or maximum flexibility of access.	A higher rate limit for customers needing larger quantities of data or greater flexibility of access.	The default choice for most multi-site organizations and energy software applications. All key features included.	Low-volume option for smaller multi-site organizations and small-scale energy software applications.
Start Now	Start Now	Start Now	Start Now

^*Request units per hour (rate limit)

When you choose your API plan you are effectively reserving a slice of our system's data-generation capacity for use when you need it. Each API plan has a rate limit, set in terms of the maximum number of "request units" per hour. The more data you fetch, the more request units you'll need. The API plan selector to the right should help you figure out what rate limit you'll need. There is also some useful advice further down this page.

^†Degree days

All API plans will let you fetch HDD and CDD from the API (and desktop app), in any base temperature(s) you choose. Extended historical data is available too (back to 2000 for many locations), though you will need more request units for each year of data you fetch.

^‡Hourly temperature data

The API Standard, Plus, and Premium plans will also let you fetch hourly temperature data from the API. (Though not via the desktop app, sorry!) It's not a replacement for degree days (as our accurately-calculated degree days already capture all relevant temperature variations), but it is a useful extra for certain sorts of specialist analysis and for user display.

^§Regression

API Standard, Plus, and Premium plans offer API access to our advanced regression functionality. Send energy data to the API and it will test thousands of regressions against it to find the base temperatures of the HDD and/or CDD that give the best statistical fit. It's a powerful feature for automated energy data analysis.

^‖Pro website access

API Standard, Plus, and Premium accounts come with free Team access to Degree Days.net Pro (worth $75 per month). This is great if you or your coworkers use the online regression tool or want easy web access to extended historical data or hourly temperature data (without it using your API request units).

^¶Priority support

If you choose an API plan with priority support, you can expect your emails to receive a response directly from our development team, within 24 hours (and usually sooner). Just include your API account key in your email to jump the queue and get straight to the developers.

API plan selector

I want to fetch data for location specified as a .

For each location I want in base temperature, covering up to year of time.

use two-stage data fetching to (1) map my locations to weather station IDs (using 1 request unit per location), then (2) fetch data by station ID to avoid duplication when multiple nearby locations share a weather station. We estimate (very approximately) that your locations will map to about stations.

Estimated request units:

From this it sounds like the plan would be ideal for you ()

To keep your data up to date you could periodically fetch the most recent figures (e.g. for the latest day, week, or month) with about request units per update.

If your won't change (e.g. if you are tracking data for ), the plan would also work well for regular data updates (like fetching the latest degree days each day, week, or month).

Instant access via secure checkout

We use a popular e-commerce service provider called FastSpring to handle billing for us. The "Start Now" buttons above all lead to FastSpring's secure website where you can enter your credit-card details for instant access to the Degree Days.net API.

Easy cancellation, any time

You can cancel your account at any time, and without penalty. It only takes a few clicks from your billing control panel (which you can access from the email receipt sent immediately after signup). After cancellation you will not be billed again, and you can continue to use the API until the end of the month that you've already paid for.

Yearly billing option

Instead of paying monthly, you can optionally pay 12 months in advance once a year. It costs the same overall, but it might be more convenient for your accounting. Click here for yearly billing.

The location-limited API plans are entry-level options that enable software to fetch regular updates of degree days for a small, consistent set of locations:

API 10 Locations	API 6 Locations	API 3 Locations	API 1 Location
$39/month	$29/month	$19/month	$9/month
Start Now	Start Now	Start Now	Start Now

Choosing the right API plan for you

The location-limited API plans are good for software fetching the latest degree days (but not hourly temperature data) each day, week, or month, for a consistent set of 1 to 10 locations. Allowed locations are set automatically as data is fetched (allowing for a limited number of changes over time). The location-limited API plans also have hourly rate limits, but you're unlikely to hit those limits if you're using your account for regular updates as designed.

The rate-limited API plans are good for all use cases, though it is important to choose a plan that is powerful enough to support the volume of data you need. Also please note that you'll need the API Standard, Plus, or Premium plan if you want to fetch hourly temperature data through the API or access the API's regression functionality.

For regular data updates from more than 10 locations, the API plan selector above should help you figure out which of the rate-limited API plans you'll need. You may be able to get by with a cheaper plan by storing data your end and fetching only the latest data each time you need an update.

For data from 1,000 or more geographic locations (postal/zip codes or longitude/latitude positions), you might want to use two-stage data fetching to save time and request units. The desktop app does this automatically. The API plan selector above will help you estimate the savings this will bring if you are dealing with 1,000 or more locations.

For ad hoc data fetching (e.g. for ad hoc projects or a software system that fetches data on demand), we suggest you plan for the maximum amount of data you expect to need in any given hour. The API plan selector above should help with this.

For one-off data-collection projects we suggest you aim to collect all your data and cancel your account before the second billing (which will come a month after you sign up) so that you only pay for the first month. Cancellation is easy – see the page on account management – and there are no hidden charges. The API plan selector above should help you decide which API plan you'll need.

If you're on a tight budget, you may be able to cut costs by spreading your data fetching across multiple hours. Though we wouldn't advise taking this too far as it can easily end up costing you more in time than it saves in API fees. It's also rather frustrating to set some software to collect data over a long period and then have your computer crash 90% of the way through!

If you're not sure what you'll need, you could do as many of our customers have: start on the API Standard plan and see how it goes. You can always change plans later if you need to. The API Standard plan offers all API features, it is powerful enough for most customers (including most customers using the desktop app), and it comes with Degree Days.net Pro website access included too. So with one API Standard account you get access to everything Degree Days.net has to offer.

Most people find that this page (and the API plan selector above) is plenty enough to help them choose an API plan, but, if you're interested in the fine detail you can read more about rate limits and request units here. You are also very welcome to email us at info@degreedays.net if you'd like more help.

Choose Your API Plan and Get Started!