Overview

Changelog

All notable improvements and extensions to the Meteonorm API are documented here.

Note that we won't make any breaking changes to API version /v1. If breaking changes are inevitable, we will release a new version at /v2 while keeping /v1 stable.

2025-12-03

• New API endpoint /climate/amy that provides Actual Meteorological Years (as opposed to Typical Meteorological Years) from 2020 onwards. /climate/amy provides the same parameters as /climate/tmy.
• New API endpoint /observation/historical that provides historical observations from 2020 onwards. /observation/historical provides the same parameters as /observation/realtime.

2025-10-24

• The /climate endpoints now support the extreme settings: poe_10_months, poe_10_year, poe_90_months, poe_90_year and worst_case_year.

2025-10-23

• The /climate endpoint now supports the polysun response format.

2025-10-17

• The /climate endpoint now supports the ida_ice_v4, ida_ice_v5 and pvsol response format.

2025-10-16

• Fixed the OpenAPI specification to accurately reflect the API's behavior: nullable: true was missing for the Values schema.

2025-10-15

• The /observation/realtime endpoint now covers the whole globe. For locations that lack satellite coverage, i.e., beyond 60°N or 60°S, we use alternative data sources.
• Bugfix: Requests with the exact combination &parameters=global_clear_sky_irradiance,weather_symbol lead to an error. This has been fixed.

2025-09-29

• The parameter snow_depth is now available for /observation endpoints (it used to return zero). snow_depth in /forecast endpoints has improved accuracy in western Europe.

2025-09-01

• Bugfix: cloud_cover values in okta (0-8) weren't always whole numbers for frequency=1_minute and frequency=15_minutes.
• Bugfix: wind_direction values were sometimes incorrect for frequency=1_minute and frequency=15_minutes.

2025-08-31

• Bugfix: precipitation values of all endpoints were incorrect by orders of magnitude for frequency=1_minute and frequency=15_minutes.

2025-07-31

• The /v1/forecast and /v1/observation endpoints now support a response_format query parameter. The available response formats are csv and json.
• The /v1/climate endpoint offers new response formats: csv, epw, tmy3, and pvsyst.

2025-07-02

• All API endpoints now return 400 "bad request" if the URL query string contains non-existent parameters. For example: /v1/forecast/precision?xxxxx=123&... will return a 400 error.