Reference · built on requestCommons signalWeather & climate

MET Norway Weather API

Location forecasts, Nordic nowcasts, marine and aviation products, and weather warnings from the Norwegian Meteorological Institute.

About

The Norwegian Meteorological Institute publishes its forecast products at api.met.no. Locationforecast 2.0 returns a JSON forecast for any coordinate on earth for the next nine days. Nowcast 2.0 gives a two-hour precipitation forecast for Norway, Sweden, Finland, and Denmark, updated every five minutes where radar coverage exists. MetAlerts 2.0 carries meteorological warnings for land, coastal, and sea regions as CAP XML, RSS, or GeoJSON. Oceanforecast, Sunrise, Tafmetar, and Textforecast sit beside them.

Through Fibric, an operator polls the products you choose, honours the Expires header, and turns a forecast or a warning into a proposal you approve: hold a shipment, start a plant earlier, or warn a shift.

This is a reference listing. It documents what Fibric would read from MET Norway Weather API and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Locationforecast 2.0: nine-day forecasts for a lat, lon, and optional altitude, as compact or complete JSON
  • Nowcast 2.0: two-hour precipitation forecasts for the Nordic area, updated every five minutes, with a RadarCoverage flag
  • MetAlerts 2.0: current and past-30-day warnings for land and marine domains as RSS, CAP XML, or GeoJSON
  • Oceanforecast 2.0 and Tidalwater 1.1 for sea state and water level
  • Tafmetar 1.0 for aviation TAF and METAR reports, and Sunrise 3.0 for sun and moon times
  • Expires and Last-Modified response headers that set when the next request may be made

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold a Nordic shipment before the snow

    Locationforecast for the delivery address and Nowcast for the depot give an operator the next nine days and the next two hours. It proposes which orders to hold and for how long, and you approve the list.

    With Weather Hold

  • Warn a shift before a red warning lands

    MetAlerts marks each warning yellow, orange, or red and says whether it is an Alert, Update, or Cancel. An operator drafts the notice for the sites inside the polygon and waits for your sign-off.

    With Severe Weather Notice

  • Start the plant when the forecast says so

    Tomorrow's hourly temperature for the building's coordinate sets the pre-heat window. The operator proposes the start time; the change is sent once you approve it.

    With Optimal Start

  • Protect coils on a freezing night

    A forecast minimum below zero at the site triggers a proposal to raise setpoints or run pumps overnight, with the forecast attached as the reason.

    With Freeze Protection

Requirements

  • A User-Agent string with your application name and a contact address, sent on every request
  • Coordinates truncated to four decimals; more precision returns 403 Forbidden
  • A cache that keeps each response until its Expires time and re-requests with If-Modified-Since
  • Clients that follow redirects, accept gzip, and use HTTPS
  • Credit to MET Norway wherever the data is shown
Authentication
No key. Every request must carry a User-Agent header naming your application and a contact email or website; missing or generic agents get 403 Forbidden.

Limits

  • Anything over 20 requests per second per application requires special agreement with MET Norway
  • Nowcast covers only the Nordic area and depends on working radar coverage at the requested point
  • MetAlerts filters by coordinate or Norwegian county number and covers MET Norway's own warning areas
  • Mobile clients may poll at most once every 10 minutes for notifications and must not fetch while inactive

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request MET Norway Weather API ↗

Questions and answers

Do I need an API key for api.met.no?
No. The API is open, but the Terms of Service require a User-Agent header that identifies your application and gives a contact email or website. Requests without one, or with a generic agent such as a library default, are answered 403 Forbidden. Fake identification strings lead to a permanent ban.
How far ahead does Locationforecast go, and where?
Nine days for any coordinate on earth. The compact endpoint returns the most used parameters; complete returns all values. Pass lat and lon with at most four decimals and, where you know it, altitude in whole metres.
How often may I poll?
Not before the time in the Expires header of the last response, and then with If-Modified-Since set to the Last-Modified value you stored. Nowcast updates every five minutes. Sustained traffic above 20 requests per second needs an agreement with MET Norway.
Ask about MET Norway Weather API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.