As WattTime continues to ‘bend the curve’ of emissions reductions, we’re excited to announce the release of our upgraded API (version 3 or v3), which includes new regions and data signals in addition to a more refined and intuitive schema. By expanding to new countries and regions, we’re enabling our partners to bring emissions-reducing technology to a greater global audience. With additional grid signals, we’re able to maximize human health benefits in addition to greenhouse gas (GHG) reductions.
The v3 API brings many improvements, including more intuitive and descriptive data delivery, error handling, and more. We don't undertake changes to our API lightly. We think the upgrades we've made in API v3 will be well worth the effort, as they will unlock greater opportunities for emissions reductions. We're here to support our partners as they begin using the new API.
New Countries and Regions
We have also released data for 12 new countries, which will only be available in API v3:
Check out our coverage map to see our full coverage, now with unique map layers for each data signal we offer through the API.
New Data Signals
In addition to CO2, the new API now offers our health damage data signal, which estimates the damage to human life and health caused by emissions from electricity generation based on the time and place that electricity is used. While currently only available in the US, this signal can be used to make decisions that reduce negative impacts on human life and health. IoT and EV companies have already begun using it as an input signal to device scheduling optimization, or to create a UI element advising users when to run appliances or plug in an EV. It can be used in tandem with the marginal operating emissions rate (MOER) to co-optimize device operation to reduce GHG emissions and damage to human health.
We’ve also added an average operating emissions rate (AOER), which is the average emissions rate (in lbs of CO2 per MWh) of all the generators operating at a particular time, weighted by their energy output. Using this signal for load shifting wouldn’t reduce emissions, but many companies find the data helpful for calculating total annual footprint for GHGP Corporate Standard, Scope 2.
To learn more about the different signals we provide, visit our data signals page.
Refined Handling of Real-time and Historical Data
Two of the biggest changes between our v2 and v3 API are our handling of real-time and historical data.
“Real-time” data (formerly found in both the /v2/data and /v2/index endpoints), used to vary in recency, typically from five minutes old up to six hours. Now, all real-time data is always available within five minutes (in the /v3/forecast endpoint, the first data point applies to the current five-minute period). This provides a single, more reliable place to look for the data that apply to right now.
“Historical” data (formerly found in both the /v2/data and /v2/historical endpoints) used to be created typically within five minutes to six hours, but was never changed or updated after that. Now we’ve designed v3 such that we can still deliver historical data within a few hours (in the /v3/historical endpoint), but we can update those data later if more or better source data for a particular data point become available (data points are not overwritten, but additional points for the same timestamp become available). This allows us to maintain a historical database of emissions data that is more representative of the best available source information.
We want this transition to be as easy as possible and worth the effort to upgrade. We’ve prepared a number of resources to guide our partners through the transition and help with getting acquainted with the new API, new regions, and new signals.
WattTime will host a Q&A webinar about the new API and new features on Tuesday, January 23, at 11:30 a.m. PST / 2:30 p.m. EST. Learn more and sign up for the webinar here, and if you miss the webinar, the recording will be accessible on-demand using the same page after the event concludes.
API Version 2 Support
API v2 will continue to be supported until June 2024. While your upgrade to API v3 will be optional for approximately the next six months, we encourage you to proactively plan for your transition so that we can support you along the way if needed.