Introduction
Integrate with UWA once; let your self-hosted gateway handle eligible upstream APIs.
On this page 3 sections
#What UWA is
Universal Weather API (UWA v1) is an MIT-licensed, self-hosted weather and environmental data gateway written in Go. It replaces multiple client-side weather API integrations with a single unified API. You configure upstream provider credentials once on your server. For each location request, UWA validates coordinates (or resolves an unambiguous place name), evaluates geographic and policy eligibility per data category, ranks available candidates deterministically, normalizes the selected provider response into that category’s canonical schema, and falls back to another eligible provider on classified failure.
UWA does not operate weather stations, issue proprietary forecasts or use AI/LLM inference. It only accesses upstream providers that your configuration and licensing permit.
#Release profiles (lean_v1 vs full_experimental)
UWA v1 supports ten protected capability routes across eight product families, governed by APP_RELEASE_PROFILE:
lean_v1(Default in all environments; mandatory in production/staging): ExposesGET /v1/datasets,GET /v1/weather,GET /v1/forecast,GET /v1/forecast/daily,GET /v1/geocode, and opt-inGET /v1/astronomy, plus/health,/readiness, and/liveness.full_experimental(Allowed only in development/test): UnlocksGET /v1/air-quality,GET /v1/history,GET /v1/marine, andGET /v1/alerts, as well as experimental adapters (APP_ENABLE_PUBLIC_NOMINATIM,APP_ENABLE_US_NWS,APP_ENABLE_BRIGHT_SKY).
Live provider calls, real PostgreSQL/Redis acceptance, Windows service operation and upstream commercial terms require operator verification in your target environment.
#Your path
Begin with the local quickstart, check the provider matrix, then read the API reference and multi-category /v1/datasets endpoint. The website itself runs without a gateway or external account.
docs/openapi.yaml (lean_v1) and docs/openapi.experimental.yaml · Verify against your build before production use.