tiny weather ============ Current conditions and a ten-day forecast for a point. One endpoint. # a token from the centre, then the forecast TOKEN=$(curl -su "$TINY_KEY_ID:$TINY_KEY_SECRET" \ -d grant_type=client_credentials \ -d audience=https://weather.tiny.kjuulh.io \ -d scope=api:read \ https://tiny.kjuulh.io/v1/tokens | jq -r .access_token) curl -H "Authorization: Bearer $TOKEN" \ "https://weather.tiny.kjuulh.io/v1/forecasts?lat=55.6761&lon=12.5683" Parameters lat, lon required, decimal degrees include current,hourly,daily (default: all three) hours 1-72, default 48 hourly RECORDS, not elapsed hours days 1-10, default 7 calendar days INCLUDING today timezone IANA name, default UTC e.g. Europe/Copenhagen Unknown or repeated parameters are refused, so a typo is a 400 rather than a quietly different answer. A fixed UTC offset is refused too: it cannot follow a daylight-saving change, and ten days can cross one. Also GET /openapi.json the schema GET /health/live process is up GET /health/ready cache, upstream and metering counters Reading a response cache.status is hit, miss, revalidated, stale or degraded. "degraded" means the forecast provider is unreachable and this is the last good copy we hold; cache.degraded is true and a Warning header is set. Honour Cache-Control and you will not be billed for requests you skip. daily[].complete is false for a day the forecast only partly covers, which is normal for today and for the last day. What it does not do History, severe-weather alerts, radar, air quality, marine, and place-name lookup. Each needs a different source with different terms. Data Forecasts come from MET Norway (the Norwegian Meteorological Institute), under NLOD 2.0 and CC BY 4.0: https://data.norge.no/nlod/en/2.0 tiny weather snaps coordinates to a grid, selects a subset of the published parameters, renames conditions and aggregates days. Every response carries the full notice in its "attribution" field; reproduce it where you show the data. MET Norway does not endorse tiny weather.