API changelog

METAR-sourced current conditions

Real-time current conditions are now supplemented by live METAR station reports, improving accuracy for locations near airports and dense observation networks.

ECMWF IFS/AIFS model added to forecast pipeline

European Centre for Medium-Range Weather Forecasts (ECMWF) IFS and AIFS models are now blended into the forecast pipeline alongside GFS and HRRR, delivering improved accuracy across Europe and the North Atlantic.

Wet-bulb temperature field

wetbulb_c · wetbulb_f

Wet-bulb temperature is now returned across Realtime and Forecast responses. Values are computed using a psychrometric method for improved accuracy under high-humidity and extreme heat conditions.

Weather alerts expanded to 50+ countries

Government-issued severe weather alert coverage has been significantly expanded via WMO CAP feeds, now spanning 50+ countries with polygon-level geographic resolution for more precise alert boundaries.

Improved rain & snow probability accuracy

chance_of_rain · chance_of_snow

Forecast precipitation probability values have been recalibrated to better reflect local variability. Previous versions could produce uniform probability clusters across extended forecast periods; these are now more dynamically distributed.

New weather condition codes — dust, smoke, haze, sandstorm & pollution

37 new weather condition codes have been added to cover atmospheric visibility phenomena previously absent from the API. New conditions include Sandstorm, Blowing dust, Widespread dust, Smoke, Haze, Light haze, Dense haze, Volcanic ash, and multiple severity levels of dust and pollution events. The condition.code and condition.text fields in all API responses (Realtime, Forecast, History, Future, Marine) will now return these conditions where applicable. All 40 supported languages have been updated with translations for the new codes. Full code reference: weatherapi.com/docs/#weather-icons.

MCP server published — weatherapi-mcp

WeatherAPI.com is now accessible as a Model Context Protocol (MCP) server. Developers can connect any MCP-compatible AI agent or IDE directly to live weather data without custom glue code. Published to the npm registry as weatherapi-mcp and listed on Glama.ai.

llms.txt published

A machine-readable llms.txt file is now available at weatherapi.com/llms.txt, giving large language models a structured summary of the API surface for use in AI-assisted development workflows.

850 k+ registered developers

The platform reached 850,000 registered developers — a milestone reflecting four years of growth since launch. Average API response time continues to hold at ~200 ms globally across 4 M+ covered locations.

Weather Maps API — live tile layer

GET /maps/tiles/{layer}/{z}/{x}/{y}.png

Weather map tiles (temperature, precipitation, wind, cloud, pressure) are now available for the next 3 days in 1-hour intervals, UTC-aligned. No API key required; free to use on any plan. Tile path templates and sample HTML integration snippets are provided in the docs.

Pollen data — forecast, realtime & history

pollen=yes

Pollen forecast is now available on Pro+ and above plans via the Realtime, Forecast, and Future APIs. Pass pollen=yes to receive grass, tree, and weed pollen indices. Enterprise clients also get pollen history back to 1 January 2010.

Wind at 100 m altitude (Enterprise)

wind100mph=yes · wind100kph=yes

New optional parameters on the History API return wind speed at 100 m height — useful for renewable energy, aviation, and construction applications. Available to Enterprise clients only.

Selective response fields — current, day & hour filtering

current_fields= · day_fields= · hour_fields=

Developers can now pass comma-separated field names to trim API responses to only the data they need. Reduces payload size and speeds up parsing for bandwidth-sensitive applications.

Swagger spec updated to v1.0.2

The OpenAPI / Swagger specification has been updated to reflect all endpoints and new parameters added through 2024–2025. Available on SwaggerHub for interactive testing without leaving the browser.

Solar Irradiance data (Enterprise)

solar=yes

Historical solar irradiance data from 1 January 2010 onwards is now available through the History API for Enterprise plan customers. Supports solar energy, agriculture, and climate research use cases.

Evapotranspiration (ET₀) parameter

et0=yes

Reference evapotranspiration (ET₀) is now returned from the Forecast and History APIs for Business and Enterprise plan users. Widely used in agricultural irrigation scheduling and hydrology modelling.

14-day forecast extended from 10 days

The Forecast API now returns up to 14 days of hourly and daily weather data for all paid plans. The days parameter accepts values 1–14.

Bulk Request — multi-location in one call

q=bulk

Pro+, Business, and Enterprise users can now send multiple locations in a single API request. Each location counts as one call. Supported across all API methods except Search.

Future Weather API — up to 365 days ahead

GET /future.json

A new Future API endpoint delivers 3-hourly forecasts for any date between 14 days and 365 days in the future. The dt parameter accepts any target date in that range.

Marine Weather & Tides API

GET /marine.json · tides=yes

Marine weather data is now available, returning swell height, swell direction, swell period, water temperature, wind wave height, and significant wave height. Pass tides=yes to include hourly tide predictions for coastal and port locations.

15-minute interval data (Enterprise)

tp=15

Sub-hourly weather data at 15-minute intervals is now available on the Forecast and History APIs for Enterprise plan customers. Pass tp=15 to activate. Useful for energy trading, transportation, and precision agriculture.

Historical data extended to 1 January 2010

The History API now covers data from 1 January 2010 (previously limited to 2021). Air quality history starts from 1 March 2021; all other weather variables go back to 2010.

History API date-range query (end_dt)

end_dt= · unixend_dt=

Pro plan and above can now request up to 30 days of historical data in a single call using the end_dt (or unixend_dt) parameter, removing the need to loop day-by-day for short date ranges.

Sports API

GET /sports.json

A dedicated Sports API endpoint now returns upcoming and in-play football, cricket, and golf fixtures enriched with local weather conditions at the venue — helping sports and fantasy platforms add weather context at no extra integration cost.

40-language multilingual support

lang=

The condition.text field in all API responses can now be returned in 40 languages including Arabic, Chinese (Simplified and Traditional), French, German, Hindi, Japanese, Korean, Portuguese, Russian, Spanish, Turkish, Urdu, and more. Pass the appropriate lang code in the request.

WeatherAPI.com launches

Public launch of WeatherAPI.com — a developer-first weather data platform built from the ground up with JSON and XML RESTful access, HTTP and HTTPS support, and a free tier with no credit card required. The initial release ships with Realtime, Forecast (3 day), Search/Autocomplete, IP Lookup, Time Zone, and Astronomy endpoints.

Air Quality (AQI) data added

aqi=yes

Air quality index data is now available across Realtime, Forecast, and History APIs. Covers CO, O₃, NO₂, SO₂, PM2.5, and PM10 pollutant gases along with EPA and DEFRA index values. Pass aqi=yes to include AQI in any response.

Weather Alerts endpoint

GET /alerts.json · alerts=yes

Government-issued severe weather alerts (USA, UK, Europe, and rest of world) are now returned via a dedicated Alerts API and as an optional field in Forecast responses. Pass alerts=yes in Forecast requests to include alerts inline.

History API — hourly historical weather

GET /history.json

Historical hourly weather data is now available from 1 March 2021 onwards on launch. Supports location query by city, lat/lon, postcode, ZIP, or IP. The dt and unixdt parameters control the date requested.

SDK libraries published on GitHub

Official client SDKs are published to github.com/weatherapicom covering popular languages and frameworks to reduce boilerplate integration work. Community contributions welcomed via pull request.