DOCS / UWA V1 RELEASE CONTRACT SELF-HOSTED GATEWAY
GET /v1/datasets
Multi-category orchestration in one request (200 OK or 207 Multi-Status)
On this page 4 sections
#Request
Required scope: per requested dataset. Registered in internal/routing/router.go (active in default lean_v1 profile).
#Parameters
| Parameter | Type | Notes |
|---|---|---|
datasets | string | Comma-separated list of 1–8 datasets (e.g. weather,forecast,astronomy) |
lat, lon | number | Coordinate pair, or use location / q place name |
location, q | string | Place name (resolved when strict place resolver is enabled, or forwarded to geocode) |
| string | Dataset-scoped parameter such as forecast.points=24 or geocode.limit=1 |
#Request example
curl -H "X-API-Key: YOUR_GATEWAY_KEY" "http://127.0.0.1:8080/v1/datasets?datasets=weather,forecast&lat=21.21&lon=81.43&forecast.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
Caller must hold every requested dataset scope upfront. Returns 200 OK when all succeed, 207 Multi-Status with meta.partial=true when some succeed, or 503 if all fail.
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.