Documentation
DocumentationGET /v1/forecast
DOCS / UWA V1 RELEASE CONTRACT SELF-HOSTED GATEWAY

GET /v1/forecast

Bounded modeled forecast points (forecast.v1)

ONE GATEWAYCoordinates → eligible provider → canonical responseWhy UWA
On this page 4 sections

#Request

Required scope: forecast:read. Registered in internal/routing/router.go (active in default lean_v1 profile).

#Parameters

ParameterTypeNotes
lat, lonnumberCoordinates, or place text when APP_WEATHER_PLACE_RESOLVER=strict
location, city, qstringOptional place text when strict place resolution is configured
pointsinteger1–168 points; default 24; not necessarily hours
providerstringOptional override

#Request example

curl -H "X-API-Key: YOUR_GATEWAY_KEY" "http://127.0.0.1:8080/v1/forecast?lat=21.21&lon=81.43&points=24"

Verified against the UWA v1 router and request parsers. Replace YOUR_GATEWAY_KEY and configure an eligible upstream provider.

#Availability and provenance

Operator configuration required

Forecast models, not measured observations. Enforces 25–50 km coordinate drift ceilings.

Successful responses return canonical data plus meta (provider attribution, cache/fallback state, request correlation, and meta.partial on /v1/datasets). Refer to docs/openapi.yaml and docs/openapi.experimental.yaml for complete schema definitions.

Canonical contracts: docs/openapi.yaml (lean_v1) and docs/openapi.experimental.yaml · Verify against your build before production use.

Search local documentation. No external requests.

↑↓ to move · Enter to openESC to close