.jpg&w=3840&q=75)
We're excited to announce the launch of One Call API 4.0, the next generation of One Call product family, and the significant upgrade after One Call 3.0.
One Call API 4.0 is a unified weather intelligence API built for developers, digital products, dashboards, analytics platforms, AI workflows, and enterprise weather integrations. It delivers seamless access to current, forecast, historical, and alert data through a single product family and a timeline-based architecture, powered by the convergent OWHL™ OpenWeather Hyper-Local Forecasting Model, updated every 10 minutes.
The API is designed for products and platforms that need both real-time awareness and deeper weather context. It includes current weather conditions, minute-by-minute precipitation data for the next 60 minutes, 15-minute forecast data for the next 48 hours, hourly weather timelines covering 47 years of history and 48 hours of forecast, daily timelines covering 47 years of history and up to 1.5 years ahead, and detailed weather alerts from national agencies.
This makes One Call API 4.0 suitable for a wide range of industries, including consumer weather applications, travel and mobility, logistics and supply chain planning, agriculture, energy and utilities, insurance, retail, smart city, safety monitoring, and business intelligence platforms. For companies building weather-aware services, it reduces integration complexity and helps turn weather data into operational, customer-facing, or analytical value.
Use case: logistics and mobility
For logistics, delivery, and mobility platforms, One Call API 4.0 can support more responsive route planning and operational decision-making. Minute-by-minute and 15-minute forecast data can help identify short-term precipitation, changing visibility, wind, or temperature conditions that may affect journeys, delivery timing, field teams, or customer notifications. Combined with alerts from national weather agencies, this allows platforms to move from simple weather display to proactive weather-based risk management.
Use case: retail and demand planning
Retailers can use historical and forecast weather data to better understand how weather affects customer behaviour, stock demand, and local operations. For example, daily and hourly timelines can support analysis of how temperature, rain, snow, or heat events influence footfall, delivery demand, seasonal product sales, or staffing needs. By combining past weather records with forward-looking forecasts, businesses can make more informed decisions around inventory, promotions, and local planning.
Use case: energy and utilities
Energy and utility companies can use One Call API 4.0 to support forecasting, infrastructure monitoring, and operational planning. Weather conditions such as temperature, wind, precipitation, UV index, and severe weather alerts can influence energy demand, renewable generation, maintenance planning, and risk assessment. With both historical depth and near-term forecast granularity, the API can support models that need to understand past conditions while preparing for upcoming weather-driven changes.
What's included
One Call API 4.0 ships with six endpoints:
- Current weather conditions
- Minute-by-minute forecast for the next 60 minutes
- 15-minute forecast timeline for the next 48 hours
- Hourly weather timeline - 47+ years of history plus 48 hours of forecast
- Daily weather timeline - 47+ years of history plus up to 1.5 years ahead
- National weather alerts with detailed alert metadata
What's new in One Call 4.0:
More granular short-term forecasting
One Call 4.0 introduces a dedicated 15-minute timeline covering the next 48 hours. Where 3.0 offered 1-minute, hourly, and daily coverage, the new 15-minute resolution fills a meaningful gap for applications that need fine-grained near-term data without the overhead of per-minute granularity across a full two-day window.
More modular data access
While One Call 3.0 was structured as a single all-in-one response, One Call 4.0 is designed as a modular product with focused, independent endpoints, one for current conditions, one for weather alerts and another one for each timeline step. This makes it easier to fetch only what you need, reducing payload size and simplifying integration logic.
Better time-series workflows
History and forecast are now combined into unified hourly and daily timeline endpoints. For dashboards, analytics tools, and planning applications that need a continuous, unbroken sequence of weather data, this removes the need to stitch separate requests together.
Stronger alert workflows
Alert references are embedded directly in weather responses, and a dedicated alert-detail endpoint allows drill-down into full alert metadata. Building alert-aware experiences from consumer apps to enterprise monitoring tools is now considerably cleaner.
API behavior: pagination
Timeline endpoints return fixed-size batches of records per response. To navigate beyond a batch, use the next and prev URLs returned directly in the API response - forward and backward navigation through any weather timeline. Each paginated request counts as a separate API call under the existing subscription model.
No changes to pricing
One Call API 4.0 continues on the "One Call by Call" subscription model with pay-per-use billing above the free daily limit. Users can set any limits in the Personal account to control expenses. If you have a currenta One Call 3.0 subscription you need to subscribe to One Call 4.0 separately.
Start here and follow the instructions to proceed: https://openweathermap.org/api
Full documentation is available at openweathermap.org/api/one-call-4.
More information about the product: https://openweathermap.org/api/one-call-4-desciption#overview