Degree Days

Degree Days

Weather Data for Energy Saving

Choose a Plan for Instant Access to the Degree API

(This page offers the API plans with yearly billing. Click here for monthly billing instead.)

The Degree 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 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 following location-limited plans enable software to fetch regular updates of degree days for a small, consistent set of locations:

1 Location 3 Locations 6 Locations 10 Locations
$108/year $228/year $348/year $468/year

The following rate-limited plans offer greater flexibility and access to larger quantities of data. They have no location limits. The higher the hourly rate limit (request units per hour*), the more data you can fetch in any given hour:

Basic Standard Plus Premium
$588/year $2,340/year $8,340/year $1,995/month
Up to 100
request units per hour*
Up to 1,000
request units per hour*
Up to 4,000
request units per hour*
Up to 12,000
request units per hour*
Hourly temperature data Hourly temperature data Hourly temperature data
Pro website access Pro website access Pro website access
Priority support§ Priority support§
Low-volume option for smaller multi-site organizations and small-scale energy software applications. The default choice for most multi-site organizations and energy software applications with moderate load. A higher rate limit for greater data-calculation throughput and flexibility of access. Our highest rate limit for companies needing large quantities of data or maximum flexibility of access.

*Request units per hour (rate limit)

When you choose your account plan you are effectively reserving a slice of our system's data-generation capacity for use when you need it. Each account 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 estimator to the right should help you figure out what rate limit you'll need. There is also some useful advice further down this page.

Hourly temperature data

Standard, Plus, and Premium accounts will also let you fetch hourly temperature data through 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.

Pro website access

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

§Priority support

If you choose an account 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.

Request-units estimator

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 map my locations to weather-station IDs (using 1 request unit per location) and then fetch data from the station IDs directly. We estimate (very approximately) that your locations will map to about stations.

Estimated request units:

From this it sounds like the account 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.

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 API.

FastSpring's payment system accepts Visa, MasterCard, American Express, Discover, and PayPal.

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 year that you've already paid for.

Monthly billing option

Most of our customers pay monthly. The overall cost is the same, but monthly billing may be better if you think you'll want to cancel or change plans. Click here for monthly billing.

Choosing the right account plan for you

The location-limited plans are good for fetching the latest degree days (but not hourly temperature data) each day, week, or month, from a consistent set of up to 10 locations. Allowed locations are set automatically as data is fetched (allowing for a limited number of changes over time). The location-limited 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 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 Standard, Plus, or Premium plan if you want to fetch hourly temperature data through the API.

For regular data updates from more than 10 locations, the request-units estimator above should make it easy to figure out which of the rate-limited 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 request-units estimator 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 request-units estimator 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 request-units estimator above should help you decide which 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, we suggest you do like many of our customers have: start on Standard and see how it goes. You can drop us an email any time to change your account plan, and we can usually provision plan changes very quickly (though it can take a day or two if we need to add significant data-generation capacity to our system).

Most people find that this page (and the request-units estimator) is plenty, but, if you're interested in the fine detail you can read more about rate limits and request units here. You are also most welcome to contact us if you'd like more help.

Choose Your Account and Get Started!

© 2020 BizEE Software - About | Contact | Privacy | Web Tool | API | Integration Guide | API FAQ | API Sign-Up