Release Notes


Probabilistic Forecast is now Available!

New probabilistic Forecast Is now available for many of the API Data Layers!

NEW API PRODUCT!! Events Timeline is now available!

Events timeline let's you get the timeframes in which weather conditions are available for a location



Simple Insights syntax product 🎆,

New Insights syntax. adding rules to our insights API

new DPL:

Low level winds


NEW API product 🎆,

New Lean endpoints:





We added some exciting features to our APIs. We support our agriculture customers with new Growing Degree Days data fields, we expanded our historical API from the last 7 years to 22 years for all historical parameters, and we made a massive step towards helping governments and companies predict and prepare against floods by releasing our high-resolution flood index product.
We released new data fields for our Maritime offering: seaSurfaceTemperature, seaCurrentSpeed, seaCurrentDirection, and tides.
And we also released new time Formats to be used as startTime and endTime parameters.


We expanded our Historical API with cloudCover data field to equip energy companies with the required data for energy consumption prediction. We've added new statistical aggregation and now offer P5, P50, P95.
Our proprietary wildfire smoke index model is complete and available through the Timeline API.


NEW API product 🎆, the Historical API is now available and can be used to research and validate past weather events to help us learn and better prepare for the next one.
We've also added precipitation intensity by type to our Timeline API. You can now request rain intensity, freezing rain intensity, snow Intensity, and sleet intensity.
This quarter we introduced bulk tagging capabilities to our Locations API and our Insights API.


Our API grows 😃 we've added a new API Notifications endpoint, upgraded our weather visualization capabilities with beautiful Map tiles, and created a new set of weather codes to describe mixed weather condition during the day and night.


This quarter we focused on enhancing the API with new data including two new data layers: Flood Index and Lightning Flash Rate Density.
We've also added Rain Accumulation data field to the Timeline API. The rain accumulation data improve our precipitation products and supports worldwide 4.5 days forecast.


Historical Weather Data. Our APIs now support 48 hours of historical weather data by using '1d' and '1h' timesteps.
Timeline API Enhancement. Providing an hourly forecast for 14 days! by using '1d' and '1h' timesteps.

Last quarter we introduced severe weather events (SWE) and this quarter we add Insights support for SWE by using the Insights API.

New quarter, new data layers :)

  • UV index data layer which measures the strength of the sunburn-producing ultraviolet radiation, according to international standards.
  • Snow Accumulation data layer measures the amount of snow that has fallen.
  • Ice Accumulation data layer measures the amount of freezing rain that has fallen.

Polygon and Polylines options were added to our Insights and Alerts APIs.


Severe Weather Events (SWE) Introducing SWE through webhooks. It's now possible to receive webhooks of upcoming severe weather events based on Severe Weather Hazards (SWH).
Available SWH:

  • fires
  • wind
  • winter
  • air
  • thunderstorms
  • tornado
  • floods
  • fog
  • temperature
  • tropical
  • marine

Timestep Check out the new "best" timestep. The best interval provides the best available data for the requested parameter based on the requested region.

Homepage We are excited to introduce our new homepage, carefully designed to include resources, guides, and API usage analytics.

New Data Layers As we constantly working on adding new data layers we are happy to announce land, soil, and maritime data are now available through the Timeline API. The new data enables new business use cases and enhances our insights and alerts offering.


Today, we’re introducing the new Data and Tiles APIs, completely rebuilt from the ground up on top of our unified platform.

Over the past few years, we learned about your use cases, your data needs, and what we can do better. We also learned a lot from our developer community of 15K and counting, and participants of our Early Access Program who have provided valuable feedback that has been essential in helping us define our new API.

We’re committed to delivering a world-class experience for weather intelligence and have set out to build the new API on a completely new foundation.

With this new foundation, developers can expect to see a modern and more thoughtful API such that:

  • Single data call: You asked and we listened. We restructured the API to introduce an all-in-one endpoint allowing you to make any weather queries - be it historical, realtime, and/or forecast data - within the same response in a lean and flat payload. No more repetitions of units and unexpected nested variables.
  • Graceful error handling: If there’s one thing that every programmer knows for sure, it’s that nothing ever works perfectly, every time, all the time. Version 4.0 provides more accurate and consistent error codes, alongside descriptive warning messages that are so helpful they’re almost as pleasant as getting a handwritten letter in the mail.
  • Revamped developer dashboard: Getting new developers up and running more quickly than ever - is where you can see all of your keys and entities, set up your webhooks, view analytics and overall usage data. Expect more exciting updates soon, like interactive insights builders to structure your conditions tree with just a few clicks and creating new locations directly from the map.
  • New design standards: The nextgen API was built in uniform, and tells a story of how weather intelligence can best serve your needs. It presents a more modern approach towards RESTful APIs, standardized naming conventions and formats, pagination across endpoints. We also added usage endpoints, that allow you to make sure you’re consuming your quotas in a controlled fashion.
  • Documentation: We want you to be ecstatic when you talk about our documentation, and so with the release of our new endpoints we have also completely rebuilt our platform documentation where you can find comprehensive information and developer resources to support your journey in building on top of our new endpoints. Keep an eye out for our public API Design Guidelines coming out soon.

Moreover, it allows us to be flexible and nimble in adding new functionality more often, and so we have built some of the most requested features, including:

  • Cutting-edge models and data layers: The new API features our much-improved weather information, from 1F through UP, to CCL. With the new foundation, we gain consistency and continuity across our models and we plan to introduce many points at a faster pace - like soil moisture/temperature, wave height/period/direction, solar irradiance (GHI, DNI, DHI) - and more to come.
  • Polygon and polyline locations: Streamline suspension and resumption procedures by continuously observing inclement weather conditions in the vicinity of your locations. With the new location types, you can choose the right bounding box base on a GeoJSON, and get any min/max/avg values within that region to help you drive confident decisions.
  • Monitoring weather events: Stop worrying about the forecast set up alerts and dashboards that are always on and working for you. Customize your own rules to be monitored based on new operators and a rich collection of fields or use any of our industry templates to continuously and automatically track specific weather conditions before, during, and after they occur in locations of your key assets or users.
  • Weather throughout a route: Expertly gather weather implications along a travel path to gain predictability, shrink unexpected slow-downs to the bare minimum and steer clear of risks. Get any of our data fields in realtime for your own route, be it with or without layovers, in land water, or air - and, like always, globally.

The new Data and Tiles API will fully replace the v3 APIs by July 1st, 2021. To see the full list of API functionality and endpoints that are included in today’s release, head over to where can get started on the new API.

Interested in giving us feedback? Drop us a note at [email protected].

2020Q3 has taken huge strides forward with this release to modernize the API platform. Deprecating outdated, outmoded endpoints, in favor of the sleek Alerts API version 4.0 is critical to the long term utility of the platform. We gradually released this version to customers in June 2020, providing a number of long-awaited functionalities and improved experience.

To encourage those of you who haven’t yet started your upgrade, we’d like to highlight some of the features of the new version:

  • Pre-defined prior notices: Unlike the current version, which triggered out notifications every hour until the event occurs, this system allows you to configure multiple notice times, thereby significantly reducing alert fatigue.
  • “All-clear” logic: In the new structure of the alerts system, we added support to be notified at the start and end of a weather event, to allow you to declare “all-clear” signals and get your operations teams to go back to normal when relevant.
  • Advanced condition operators: Determining the correct alerting threshold requires ongoing tuning and refinement. On top of the traditional comparison operators, we added secondary filters like advanced condition in the form of operators to allow you to confine notifications to a specific local time in the day and to the ratio of occurrence within a given time frame.
  • Centralized management:The big winner in terms of saving time and energy. Now you can configure conditions once, and apply on multiple alerts - each with its own notification settings. You can also set up multiple locations to be monitored by that alerts - making weather-based automations a breeze.
  • Robust collection of data points: It’s important to have a default set of alert rules for each test since that’s what most users are going to work with. Therefore, default alert rules are a good opportunity to fine-tune the balance between false negatives and false positives. A good starting point is to select metrics that are associated with availability instead of speed, e.g. packet loss, DNS resolution, etc. And thresholds that err on minimizing false positives.
  • Descriptive webhook payload: Attributes like “severity”, “certainty“ and “urgency“ add context to reported events, alongside field values at the location, the subset of them that triggered the notification, the “name” of the location, event, and alert type.

We also removed features in this go around, which might be added down the line:

  • Multiple webhooks: For now, all alerts will be sent to the main webhook defined for the account, and can be handled differently based on the integration's business logic according to the descriptive payload. In the future, a set of webhook endpoints can be configured, in the developer website and programmatically, to receive only the types of events required by your integration, to reduce strain on your server.
  • SMS/Email notifications: We decided to opt-out of supporting delivery services as part of the API, as each customer requires a different configuration of the messages, branding, sender origins and distribution groups. Integrate the API with any of your preferred delivery service webhooks, such as Twilio, Zapier, and Sengrid, to get personalized alerts.

Alerts APIs in version 3.0 have reached their end-of-life, which includes Alerts, Groups, Group Members, and Webhooks. Unless you are an enterprise customer with access to extended support, it is probably a good idea to upgrade to the new Alerts API, version 4.0.

We continue to introduce new alert mitigation mechanisms, fields, and operators to give you more control to tailor them to your own use cases. Want to learn more? Reach out to [email protected]