Skip to content
Docs navigation

REST API

The Smarter Weather API provides a unified interface to weather data. All endpoints return JSON, serve errors as RFC 7807 problem details, and authenticate via an HTTP Bearer token.

Smarter Weather covers the 50 US states and DC only. Every route that takes a point (lat and lon, zip or location) returns 404 outside-coverage for a point outside the 50 states and DC. /v1/alerts and /v1/observations return it for a bounding box that touches no US domain (CONUS, Alaska, Hawaii); a box that touches one may still include area outside the US. /v1/weather/batch reports it per item as outside_coverage, and /v1/point with points and /v1/series/batch mark such points out_of_domain, as they do a point the check could not reach in time (retry it). If the location lookup is unavailable, the check can briefly fail open. Routes keyed by a station, radar site, forecast office or alert id, and nationwide lists, are not filtered by point, so do not treat an empty result as an all-clear. See Errors.

Single source of truth

Every endpoint, parameter, and response shape is rendered live from the canonical OpenAPI document. Each resource page below pairs that machine-rendered spec with the narrative context for when to reach for the endpoint and which data sources back it.

Authentication

Pass your developer key as an HTTP Bearer token. Keys come in two flavors: sw_live_* for production traffic and sw_test_* for CI and local development. See authentication.

Rate limits

Rate limits vary by plan and are published with the error model. See errors and rate limits.

Resources

Each page pairs the canonical spec for a resource with the narrative context for when to use it.

Full spec and tooling

For SDK generation, full-text search across every operation, or feeding the spec into another tool.