Every API release since the 2024 public launch, newest first. The docs table carries the condensed version; this is the director's cut, including the changes we'd rather not dwell on.
uv_index added to all forecast hours (previously daily-only)./v1/history (it already existed for current and forecast; history responses are big enough that JSON-to-CSV in pandas was getting old).format=xml, which we had quietly supported since v1.2 for exactly three known users. Two answered our forum post, migrated to JSON, and confirmed. The third we assume moved on to greener pastures; the XML path now returns 400 with a helpful message rather than the confusing partial parse it used to return.city= lookups for places with diacritics no longer require exact spelling. "Malmo" now finds Malmö, as it should have all along./v1/now alias (see v1.4 below). 4,100 calls hit the dead endpoint on day one, all from two scripts at what we suspect is the same university department. If that's you: it's /v1/current now, and has been for a while./v1/now, the original name for current conditions. It returned the same payload as /v1/current — two URLs, one response — and "now" turned out to be a poor name for something cached up to five minutes. Migration: replace /now with /current in any URL; parameters are identical. The alias kept working (with a deprecation header) until v1.6 removed it in November 2024.postal=1051&country=NL). Coverage is good in Europe and patchy elsewhere — we ship what the national services publish.units=scientific for people who want kelvin and m/s without doing arithmetic.tz response field on forecast endpoints, which was sometimes the location's timezone and sometimes UTC depending on how the response was cached. Migration: use timezone (always the location's) and the time fields (always local to that zone). The old field returned a fixed UTC string until v1.7 removed it.Cache-Control headers set correctly on history responses (previously max-age=300, which was too modest for immutable data).Breaking changes get at least 90 days' notice on this page and the forum, per the terms. Point releases and data fixes don't get individual entries — if the temperature in your city was wrong on a specific Tuesday, that's a forum post, not a version. Check status for anything that looked like an outage.