MET Norway
met.no · 2 records in Data APIs · JSON
Records 2
- ★ qualifiesMET Norway Weather API
Data APIsfree tieridentity anonymousno cardlimit request-rateevidence documentedstale on 2026-12-03
- caveatMET Norway Frost API
Data APIsfree tieridentity emailno cardlimit request-rateevidence documentedstale on 2026-12-03
MET Norway Weather API
Data APIs- Free allowance
- No fee, no key and no registration: Locationforecast and the other products of api.met.no answer any coordinate at up to 20 requests a second per application (total, not per client); the caller sets a User-Agent that names the application and gives a contact.
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- request-rate20 requests a second per application, total and not per client; over it requests are throttled with HTTP 429; coordinates to at most 4 decimals; 5 or more answer HTTP 403 on new products
- Evidence
- documented17 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-03checked 2026-11-02 (live); stale on 2026-12-03
| Free tier | No fee, no key and no registration: Locationforecast and the other products of api.met.no answer any coordinate at up to 20 requests a second per application (total, not per client); the caller sets a User-Agent that names the application and gives a contact. unit requests; metered on request-count; Over 20 requests a second needs a special agreement; throttled clients get HTTP 429, a missing or generic User-Agent gets HTTP 403, and coordinates are cut to 4 decimals. Locationforecast is refreshed every hour inside the Nordic area and every 6 hours elsewhere. Bulk path: the THREDDS server serves model files (NetCDF over OPeNDAP) for the Nordic and Arctic regions only, with no global files; historical observations come from the separate Frost API (see data-apis/met-norway-frost). |
|---|---|
| Price | none stated |
| Limits | |
| Binding | request-rate The 20 requests a second ceiling is shared by all users of one application; the User-Agent requirement is met by one header. |
| Identity | anonymous No sign-up and no key: the institute's capacity-building page says the service is open to anyone with no registration; only a User-Agent with an application name and a contact address, website or repository link is required. A call with no key answered HTTP 200. |
| Egress | not applicable: JSON answers; gzip compression is supported |
| Retention | not applicable: the API serves current forecasts only; model archives are on THREDDS |
| Interface | rest REST over HTTPS GET at api.met.no/weatherapi (GeoJSON forecasts; also radar, nowcast, ocean, sunrise and others); gridded model files over OPeNDAP and NetCDF from thredds.met.no (an interface term for OPeNDAP is missing) |
| Tooling | any HTTP client that sets a User-Agent; third-party client libraries are listed in the docs; THREDDS files are read with OPeNDAP clients, FIMEX or ncdump |
| Composes with | A keyless global point-forecast source for 9 days ahead with a high per-application ceiling; history comes from THREDDS archives and the Frost API, not from this endpoint. |
| Reliability | No SLA; a missing or generic User-Agent answers HTTP 403 and traffic over the limit is throttled with HTTP 429 or blocked. |
| Notes | Bulk path: THREDDS model files for the Nordic and Arctic regions; no global dump. The Frost API holds the historical observations. |
| Evidence note | documented Limits and identification rules are read from first-party pages; a keyless forecast call and an anonymous OPeNDAP call answered HTTP 200; the 20-requests-a-second ceiling was not driven. The docs link to thredds.met.no/thredds/metno.html, which answered HTTP 404. |
| Parsed numbers |
|
Evidence 17
| date | source | what it proved |
|---|---|---|
| 2026-11-02 | docs.api.met.no/doc/TermsOfService | the limit is 20 requests a second per application, counted over all clients |
| 2026-11-02 | docs.api.met.no/doc/TermsOfService | a client that breaks the terms is throttled with HTTP 429 |
| 2026-11-02 | docs.api.met.no/doc/TermsOfService | no delivery guarantee and no SLA |
| 2026-11-02 | docs.api.met.no/doc/TermsOfService | every request carries an identifying User-Agent |
| 2026-11-02 | docs.api.met.no/doc/TermsOfService | coordinates are cut to 4 decimals; 5 or more answer 403 on new products |
| 2026-11-02 | docs.api.met.no/doc/TermsOfService | not published |
| 2026-11-02 | api.met.no/weatherapi/locationforecast/2.0/documentation | not published |
| 2026-11-02 | api.met.no/weatherapi/locationforecast/2.0/documentation | Locationforecast gives 9 days ahead for any coordinate |
| 2026-11-02 | api.met.no/weatherapi/locationforecast/2.0/documentation | bulk model files cover the Nordic and Arctic regions only |
| 2026-11-02 | docs.api.met.no/doc/locationforecast/FAQ.html | forecast update cadence |
| 2026-11-02 | docs.api.met.no/doc/thredds | THREDDS serves gridded data over OPeNDAP |
| 2026-11-02 | bistand.met.no/en/weather-api | no registration is needed |
| 2026-11-02 | docs.api.met.no/doc/FAQ.html | there is no pricing model for high-volume sites |
| 2026-11-02 | probe: https://api.met.no/weatherapi/locationforecast/2.0/compact | a Locationforecast call with no key and no sign-up answered a GeoJSON forecast |
| 2026-11-02 | probe: https://api.met.no/weatherapi/locationforecast/2.0/compact?lat=59.91&lon=10.75 | the same call answered HTTP 200 |
| 2026-11-02 | probe: https://thredds.met.no/thredds/dodsC/metpplatest/met_forecast_1_0km_nordic_latest.nc.dds | the THREDDS OPeNDAP dataset descriptor of the Nordic forecast answered with no credentials |
| 2026-11-02 | probe: https://thredds.met.no/thredds/dodsC/metpplatest/met_forecast_1_0km_nordic_latest.nc.dds | the THREDDS call answered HTTP 200 |
Unknown values 1
- per object cap stated: the field does not apply to this kind of offer
MET Norway Frost API
Data APIs- Free allowance
- Free access to MET Norway's archive of historical weather and climate observations (quality controlled daily, monthly and yearly measurements of temperature, precipitation and wind, and station metadata) with a client ID issued for an email address; no numeric request quota is published.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- request-ratemore than 1 request a second on average is heavy traffic that should be cached; no hard number is published
- Evidence
- documented9 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-03checked 2026-11-02 (live); stale on 2026-12-03
| Free tier | Free access to MET Norway's archive of historical weather and climate observations (quality controlled daily, monthly and yearly measurements of temperature, precipitation and wind, and station metadata) with a client ID issued for an email address; no numeric request quota is published. unit requests; metered on request-count; Heavy traffic is defined as more than 1 request a second on average, which should be cached locally; users with high load or bad traffic patterns can be blocked. Large requests time out and are split by station or by time range. Bulk path: none beyond split requests; gridded model data are on THREDDS (see data-apis/met-norway). |
|---|---|
| Price | none stated |
| Limits | |
| Binding | request-rate Only the 1 request a second guideline is stated, so the sustained rate binds first. |
| Identity | email A client ID and secret are issued after registering with an email address; each client ID must be tied to a valid email address. The form's other fields were not readable. |
| Egress | not applicable |
| Per-object cap | requests that are too large time out; the vendor advises splitting, for example 1000 stations into 10 requests of 100 |
| Retention | not applicable: the unit is a request |
| Interface | rest REST over HTTPS at frost.met.no with Basic authentication (client ID as user name, empty password) or OAuth2; JSON-LD answers |
| Tooling | any HTTP client; examples for curl, Python and Java are published |
| Composes with | The historical-observation companion to the keyless api.met.no forecasts: station data by source, reference time and element. |
| Reliability | No delivery guarantee; clients with high load or bad traffic patterns can be blocked. |
| Notes | Observations only; forecasts are on api.met.no. |
| Evidence note | documented Identity and traffic rules are read from first-party pages; a call with no client ID answered HTTP 401, so a keyed call was not exercised. |
| Parsed numbers |
|
Evidence 9
| date | source | what it proved |
|---|---|---|
| 2026-11-02 | frost.met.no/ | Frost serves MET Norway's historical observation archive |
| 2026-11-02 | frost.met.no/auth/requestCredentials.html | an email address gives a client ID |
| 2026-11-02 | frost.met.no/authentication.html | every data request needs a client ID |
| 2026-11-02 | frost.met.no/termsofuse2.html | more than 1 request a second on average counts as heavy traffic, to be cached locally |
| 2026-11-02 | frost.met.no/termsofuse2.html | a client ID needs a valid email address; several IDs per address are allowed |
| 2026-11-02 | frost.met.no/termsofuse2.html | large requests time out and must be split |
| 2026-11-02 | frost.met.no/termsofuse2.html | part of the text of Reliability, above |
| 2026-11-02 | probe: https://frost.met.no/sources/v0.jsonld | a call with no client ID answered 401 |
| 2026-11-02 | probe: https://frost.met.no/sources/v0.jsonld | the call answered HTTP 401 |
Unknown values 1
- egress terms: the field does not apply to this kind of offer