Conditions for use of the service
In the following you will find guidelines for using the service api.met.no. The service has good capacity and can handle relatively large volumes of requests, but the capacity is not unlimited. We encourage all users to respect the guidelines so that the service will be stable.
If we see that there are situations that threaten the operation of our environment, we would consider blocking out the users/services that give bad high load/traffic patterns. If you set up your service in accordance with our policy it will increase the probability that the service is not blocked. At high total load of the service we met.no prioritize critical products such as the location forecast and text forecast at the expense of other products such as satellite images, radar images and weather maps.
If you need to get a customized delivery of weather data and products, you can see what is offered in ECOMET catalogue on www.ecomet.eu.
We only support encrypted HTTPS for security reasons. Repeated HTTP traffic is not allowed and can result in blocking.
Use the information found in any cache headers, see RFC 2616. For example, use If-Modified-Since requests if the Last-Modified header exists. Note that the If-Modified-Since header should be identical to the previous Last-Modified, not any random timestamp (and definitely not in the future).
Use a local caching proxy hosted at your site. This is especially important for "slow clients" such as mobile devices.
Do not ask too often, and don't schedule requests every hour on the dot (add a random number of minutes to the time of the requests as our data are continously updated).
Check response headers and limit traffic immediately if you receive 429 status codes from the API. Avoid continuous updating of mobile devices. Applications on mobile devices must not retrieve new data as long as the application is not in use.
Support gzip compression (Accept-Encoding: gzip, deflate) ref RFC 2616.
You should save the information on your own server if you have heavy traffic. Heavy traffic means more than 20 requests from the api per second. Please contact us if you find that your service generates more traffic than this and you do not have reduced the amount of requests by taking into account our guidelines.
Large pictures and objects, for example animations
Copy animations to your own server if you expect heavy traffic. Do the same for any other large objects. We have good bandwidth, but sites with heavy traffic which links directly to our animations, can use more bandwidth than we have taken into account. It is desirable that you inform your users about the time you retrieved the data so that they can consider whether they look at outdated data.
Add a User Agent-string (UA) in the request with the application/domain name and version number. You may also include a company email address (e.g. firstname.lastname@example.org); this is a requirement if we cannot find any contact details on your website. Company email addresses are not considered personal information for GDPR and other privacy purposes.
Deliberate breach of our TOS, as well as trying to circumvent traffic rate limiting measures will result in a permanent ban in the use of our services.
General information about the service
All weather data on the api are continually updated. New data will be made available in the service continuously. In order to receive important notifications about changes to the service we strongly suggest you either subscribe to either our api-users mailing list or RSS feed.
On products marked with "lts" (longtime support, currently on locationforecastlts) we guarantee a phase-out period of three months.
Other products have varying length of their phase-out period depending on what we consider to be reasonable.
There are no guarantees of delivery regarding this service, or possibilities to obtain an SLA.