In the following you will find guidelines for using the service frost.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.
Use the information found in any cache headers. See RFC 2616
For example, use If-Modified-Since requests if the Last-Modified header exists.
Use a proxy if possible. This is especially important for "slow clients" such as mobile devices.
Do not ask too often. Avoid continuous updating of mobile devices. Applications on mobile devices should download data when explicitly requested
by the end user (by pushing a "refresh" button, for example).
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.
If your request is too large, you will get a timeout error. Please split your request into smaller subrequests. For example, a request that specifies data
from 1000 weather stations can be split into 10 requests, each specifying 100 stations. Likewise, a long timeseries of observations can be split into
requests for N time subranges.
The API requires a unique client ID for identification. Each client ID must be associated with a valid email address.
It is possible to register multiple client IDs for each email address.
Conditions For Data Use
Data from frost.met.no are licensed and the license is found in every response. Read more about licensing and crediting
General Information About The Service
All weather data available on the API are continually updated. New data will be made available in the service continuously.
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.
The version is specified both in the URL and in the response of each endpoint (service).
Whenever the API is changed in a way that is not backwards compatible, the version number will be incremented.