THE SHORT ANSWERS / UWA V1

Common questions.
Clear technical answers.

Understand how UWA routes data, manages upstreams and preserves the boundary between source implementation and production verification.

Start building
FAQ / PRODUCT & OPERATIONS

Know what the gateway does—and what it doesn't.

These explanations are based on the UWA v1 documentation. Check the linked source contracts and release notes before deploying.

01

What is Universal Weather API (UWA)?

UWA is an MIT-licensed, self-hosted weather and environmental data API gateway written in Go. Applications integrate with UWA instead of maintaining separate integrations for every upstream. UWA selects eligible providers by data category, coordinates and operator policy, then normalizes responses to versioned schemas.

Read the introduction
02

Does UWA generate its own weather forecasts?

No. UWA is a gateway, not a weather observation network or forecast model. It retrieves permitted upstream data and validates, normalizes and attributes the results.

Review architecture
03

How does UWA select the right weather API provider?

Each requested dataset is evaluated independently. The routing engine checks geographic coverage, release profile, credentials, deployment use, provider policy and quota eligibility. It then ranks eligible candidates using deterministic rules.

Understand routing
04

What happens when a weather provider fails?

When a classified upstream or integrity failure occurs, UWA can try the next eligible provider for the same location and data category. Fallback is not guaranteed when no alternative is permitted or available.

Read fallback rules
05

Can I request weather and forecast data together?

Yes. GET /v1/datasets requests multiple supported categories for one geographic location. A partially successful request can return HTTP 207 Multi-Status with successful data and per-category errors. It is not a multi-location batch API.

See /v1/datasets
06

Can I self-host UWA and use my own API keys?

Yes. UWA is designed for deployment on infrastructure you operate. Configure authorized upstream credentials on the server. Your applications authenticate to UWA with their own scoped gateway client keys. Vendor licensing and usage restrictions still apply.

Start the quickstart
07

Which UWA capabilities are production defaults?

The lean_v1 profile covers core weather, forecast, daily forecast, geocoding, multi-category datasets and opt-in astronomy, subject to configuration and provider eligibility. The full_experimental profile adds development/test capabilities such as air quality, history, marine and alerts.

Review release limits
08

Does the Routing Explorer show live weather data?

No. The website explorer is a browser-only illustration derived from UWA routing rules. It does not make upstream requests, check real provider availability or run the Go gateway in your browser.

Open the explorer
09

Are all listed weather providers available worldwide?

No. The source includes 15 adapters, but actual eligibility depends on geographic coverage, credentials, terms, deployment use, release profile, quotas and operator policy. Source implementation does not mean live certification.

Compare providers
10

What should I verify before production deployment?

Validate provider terms and credentials, the required PostgreSQL and Redis services, explicit quotas, security settings, accepted release profile, geographic rules and live reliability under your environment. Review diagnostics and release notes before production use.

Operational checks
NEED MORE DETAIL?

Go deeper with source-grounded documentation.

Browse docs

Search local documentation. No external requests.

↑↓ to move · Enter to openESC to close