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

GET /v1/weather

Current weather observations (weather.v1)

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

#Request

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

#Parameters

ParameterTypeNotes
lat, lonnumberCoordinate pair (or use location / city / q)
location, city, qstringPlace text; resolved via strict geocoder when APP_WEATHER_PLACE_RESOLVER=strict
providerstringOptional provider override (must still pass policy)
policystringOptional routing policy override

#Request example

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

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

Requires a configured eligible weather provider. Enforces a 2-hour observation age ceiling and 50 km coordinate drift limit.

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