What you get#
Onekey exposes MET Norway as 2 endpoints behind one API key: 2 endpoints return one record (data is an object). Every answer uses the same envelope (success, data, metadata, error), the cost is reported in metadata.credits_charged, and fields are mapped onto the unified schema so the code you write for MET Norway also works for the rest of the maps, weather & space category.
Endpoints#
| Endpoint | What it does | Parameters | Credits | Status |
|---|---|---|---|---|
forecast | Current conditions and next-hour outlook (MET Norway locationforecast compact). | lat*, lon* | 1 | stable |
sun | Sun rise/set/noon times and azimuths (MET Norway) for a coordinate and date. | lat*, lon*, date* | 1 | stable |
A * marks a required parameter. Each endpoint name links to its reference page with the full parameter table, caching window and a recorded response.
Make a request#
This calls metno.forecast (1 credit, stable). Replace YOUR_API_KEY with your key; sign up, no card. 1,000 free credits cover the open-platform endpoints. Hard-to-reach platforms (X, TikTok, Instagram, Reddit, and others marked on their page) need a verified email and a purchased pack.
curl "https://api.onekey.dev/v1/metno/forecast?lat=60.1&lon=9.6" \
-H "x-api-key: YOUR_API_KEY"Fields you get back#
These unified fields come back from MET Norway, with the same names as on every other platform. The count is how many of its 2 mapped endpoints return the field; a field the source lacks is null, never missing. 11 platform-specific fields (ext.<name>) come on top, documented on each endpoint page.
| Field | Type | Endpoints |
|---|---|---|
entity.date | ISO 8601 date | 2 |
entity.category | string | 1 |
entity.createdAt | ISO 8601 date | 1 |
place.elevationM | number | 1 |
The full schema is in Unified schema.
Pricing#
Every MET Norway endpoint costs 1 credit per call. Free when served from cache (0.2 credit for a cached response over 100 KB). Invalid, failed or not-found calls are not charged. See pricing for credit packs.