Welcome to the MET Norway Weather API v.3

Norsk versjon.

api.met.no/weatherapi is an interface to a selection of data produced by MET Norway. The data are available for use under a Creative Commons license. See also separate conditions for use of the service.

All regular users of the API are strongly recommended to subscribe to our API-users mailing list as this is the only channel on which we will communicate planned changes outside the API itself (see the archives for past notifications).

For operational status and maintenance notifications, see status.met.no (please bookmark in case there is a problem with the site).

For information on available data and how to access them, please refer to the weatherapi documentation. For a list of changes since version 2, see the Release Notes for v.3.

Data owned by other institutions than MET Norway is not available for unrestricted public use. This is specified in the documentation of each product. Examples of such products are the Nordic radar images and some satellite images. Refer to the documentation of each product.

Available products:

Errornotifications 1.0
Errornotifications - Error notifications from the WeatherAPI system
Extremeforecast 1.0
Extremeforecast - Textual extreme forecast.
ExtremesWWC 1.2
ExtremesWWC - The Wettest, Warmest and Coldest places
Forestfireindex 1.1
ForestfireIndex - Reporting danger level of forest fires.
Geosatellite 1.4
Geosatellite - Images from geostationary satellites
Gribfiles 1.1
Gribfiles - Serve grib files on the coast from Oslo and Western Norway
Icemap 1.0
Icemap - Maps as images showing current ice conditions in the arctic regions.
Lightning 1.0
Lightning - lightning data delivered in UALF
Locationforecast 1.9
Locationforecast - Weather forecast for a specified place
LocationforecastLTS 1.3
LocationforecastLTS - Weather forecast for a specified place, long term support.
MetAlerts 1.1
MetAlerts - Meteorological alerts (new format that will be phased in)
Metgm 1.0
Metgm - Deliver meteorological forecast data in METGM format for defined areas
Mountaineasterobservations 1.0
Mountaineasterobservations - manual observations from DNT mountain cabins during easter.
NLAroutes 1.0
NLAroutes - Vertical cross sections for flight routes
Nowcast 0.9
Nowcast - Nowcast for a specified place.
Oceanforecast 0.9
Oceanforecast - Ocean forecast for a specified place
Polarsatellite 1.1
Polarsatellite - Images from satellites in polar orbit
Probabilityforecast 1.1
Probabilityforecast - Probability forecast for a specified place
Radar 1.5
Radar - Radar images from various locations
Radarlightning 1.1
Radarlightning - Radar images from various locations
Sigmets 1.0
Sigmets - Get sigmets and airmets for Norway
Spotwind 1.0
Spotwinds - Spotwinds in XML
Subjectiveforecast 1.0
Subjectiveforecast - Forecasts and analyses charts from the meteorologist
Sunrise 1.1
Sunrise - When does the sun rise and set for a given place?
Tafmetar 1.0
Tafmetar - Receive Taf/Metar from airports
Temperatureverification 1.0
Temperatureverification - Verification of temperature forecast.
Textforecast 1.6
Textforecast - Textual weather forecast for all parts of the country
Textlocation 1.0
Textlocation - All available textual forecasts for a given point.
Tidalwater 1.1
Tidalwater - Tidal water information
Turbulence 1.1
Turbulence - Turbulence prognosis
UVforecast 1.0
UVforecast - A prognosis of UV radiation
Upperwindweather 1.1
Upperwindweather - Upperlevel wind and weather charts
VerticalProfile 1.1
Verticalprofile - Vertical profiles of wind and weather
Weathericon 1.1
Weathericon - deliver weather icons.


Migration completed 2018-02-26

Dear API users,

as most of you probably have noticed, we upgraded api.met.no about a week ago to the new version. After some initial performance problems we managed to tune the caches so it is now handling traffic well.

Some users have reported problems accessing the API, mostly related to not handling HTTPS and/or redirects. If you are getting "Failed to get data from weather api. Reason: end tag name </body> must match start tag name <hr> from line 5" this means you are trying to parse the HTML message as XML instead of following the 301 redirect. We are also working on recommendations for users using HTTPS via local proxies.

In order to ensure stability of our own services, we have also introduced traffic rate limiting (and in some extreme cases, blocking) for some users not abiding by our terms of use. If you are receiving 429 status codes it means you are being throttled, either due to a missing/generic User-Agent header and/or excessive traffic (>20r/s).

Finally, we have noticed there is a lot of production traffic against beta.api.met.no (which was only to be used for testing) as well as api.yr.no (which has been deprecated for years). We would like to inform you that these hostnames will be removed within a few months, so please update your applications accordingly.

As always, please don't hesitate to contact us if you have problems or general enquiries.

Migration of api.met.no 2017-12-12

As previously mentioned on the mailing list, we will shortly be migrating the api.met.no domain to version 3. This has already been done for some users and should be relatively painless, provided you follow the documentation and terms of use. In particular we ask you to notice the following:

  • Use HTTPS only! Unencrypted requests are no longer supported
  • Honor redirects (301 and 303), which is used e.g. from HTTP to HTTPS
  • Semicolon as parameter separator is now deprecated, use ampersand instead
  • Make sure you have a unique, identifiable User-Agent string

Otherwise the main difference is a lot of new features and bugs that have been fixed. For more information on the changes to the interface, please see the release notes for version 3.

The migration is scheduled to take place some time during the first half of January 2018.

Change log

MetAlerts: 2018-03-08

Support for search by county number (for warnings issued after 2018-03-15)

Sigmets: 2018-02-22

No longer generates error when no SIGMETS have been issued

Textlocation: removal of gale and obsforecast, 2017-12-14

From February 2018 all gale and obs forecasts will only be delivered via metalerts. This means those elements will no longer be present in the textlocation XML, instead they must be fetched as CAP from the metalerts product on the API.

Textforecast: gale and obs soon to be discontinued, 2017-12-13

The gale and obs warnings are now available in CAP format from the metalerts section of the API, and will shortly be discontinued in textforecast. The following values will then no longer be allowed in the forecast parameter and will result in a 400 Bad Request:

  • gale
  • gale_id
  • obs
  • obs_va
  • obs_vn
  • obs_vv
Upperwindweather: Discontinued products, 2017-12-11

The following products are no longer being produced, but may be added again in the future:

pwad, pwae, pwcd, pwce, pwrd, pwre, pwbd, pwbe, pwdd, pwde

The API now also ignores files older than 2 days, to avoid serving obsolete data.

Nowcast: 2017-09-11

Added coverage method

Other data sources at MET Norway

See free meteorological data on met.no for a complete list of data services.


For questions regarding rights to and use of data, see our Licensing and Data Policy. For technical questions, contact technical personnel.