Skip to content
Open Snotel home
API

API overview

Use the REST API at /api/v1: every endpoint, the conventions all responses follow (UTC times, null for missing, the source's units and flags), request bounds and caching.

The REST API is public, read-only and needs no key. It lives under /api/v1 on this site; there is no separate API host. Every value in it keeps the source's unit and flags, and a missing reading is null, never zero.

Make a request

curl 'https://opensnotel.com/api/v1/stations/312:ID:SNTL/latest?elements=SNWD&duration=HOURLY'
{
  "station": "312:ID:SNTL",
  "data": [
    {
      "elementCode": "SNWD",
      "duration": "HOURLY",
      "ordinal": 1,
      "heightDepthIn": null,
      "unit": "in",
      "observedAt": "2026-10-23T19:00:00.000Z",
      "localDate": "2026-10-23",
      "value": 1,
      "flag": "R",
      "qualityFlag": "V",
      "isProvisional": null,
      "sourceUpdatedAt": "2026-10-23T20:05:00.000Z",
      "newestObservedAt": "2026-10-23T19:00:00.000Z",
      "freshness": { "state": "fresh", "staleAfterMinutes": 360 }
    }
  ],
  "meta": { "generatedAt": "2026-10-23T21:20:00.000Z" }
}

Endpoints

Method and pathReturnsPage
GET /api/v1/stationsA page of stationsStations
GET /api/v1/stations/{station}One station and what it reportsStations
GET /api/v1/stations/{station}/latestThe newest reading of each sensor, with freshnessObservations
GET /api/v1/stations/{station}/observationsReadings over a date rangeObservations
GET /api/v1/stations/{station}/contextSnowpack Context: recent change and comparison with historySnowpack Context
GET /api/v1/stations/{station}/climatologyA water year against the station's WY1991–2020 bandSnowpack Context
GET /api/v1/rankingsStations ranked by recent gain, depth or anomalySnowpack Context
GET /api/v1/stations/{station}/weatherNWS weather around the station: nearby observations, forecast, alertsWeather
GET /api/v1/stations/nearestThe stations nearest a pointNearest stations
GET /api/v1/resortsA page of North American ski resortsResorts
GET /api/v1/resorts/{resort}One resort with its operating area and provenanceResorts
GET /api/v1/coverageHow complete and current each data source is, with known gapsCoverage
GET /api/v1/openapi.jsonThe OpenAPI documentOpenAPI

{station} is always the station triplet, such as 312:ID:SNTL. Percent-encoded colons work too. {resort} is a resort's slug, such as bogus-basin-mountain-recreation-area.

Conventions

  • Times. Instants such as observedAt are ISO 8601 in UTC. localDate is the station's calendar day, from the fixed offset in utcOffsetMinutes; see time and dates.
  • Missing values. value is null when the source reported none. It is never zero, and the row is still returned so a gap can be told from a quiet sensor.
  • Flags and units. flag, qualityFlag and unit are the source's, unchanged; quality explains them. originalValue keeps the reading as first received when the source later edited or blanked it.
  • Observed unless labeled. The station, latest and observations endpoints return observed values only, and no snowfall is computed from depth. The Snowpack Context endpoints add derived values (changes, comparisons with history, accumulation events), each labeled derived with the derivation version that produced it. The weather endpoint also returns NWS forecasts and observations from nearby NWS stations, and labels every value with its kind. See provenance.
  • meta.generatedAt. When the answer was computed. Answers are cached, so it can be a little earlier than the response.

Bounds

Requests are bounded so no call can ask for the whole dataset.

LimitValue
Stations per page1 to 500, default 100
Resorts per page1 to 500, default 100
Elements per request10
Daily observations per request366 days
Hourly observations per request31 days
Readings per response20,000
Nearest stations25, within 500 km
Ranking entries1 to 50, default 10

A request over a limit answers 422 with range_too_large and the limit; see errors.

Caching

Reads are cached and served with public Cache-Control headers. Latest conditions are shared for about a minute, and a new reading invalidates them as soon as it is stored. Station metadata, the resort registry and settled history are cached for an hour. A range that reaches into the last three days, which can still be revised, is cached for five minutes. Freshness is judged when the response is sent, not when the data was cached.

Usage & pricing

The API is free, without a key, for personal, non-commercial, educational, research, journalistic and nonprofit use, and for evaluating or prototyping a commercial product, within the rate limits (Terms, section 3).

Commercial use needs a commercial plan or a written agreement (section 4). That covers a paid, subscription or ad-supported product, internal use by a for-profit business, AI or agent products that call the API for their users, reselling, redistributing, bulk downloading, caching or mirroring responses as a dataset or service, and any use above the free rate limits. Until self-serve plans are available, Pricing has the contact.

Clients also agree to the API and MCP rules, such as respecting 429 responses and Retry-After (see rate limits). The Terms of Use and Privacy Policy cover the rest.

The machine-readable reference

GET /api/v1/openapi.json is the OpenAPI 3.1 description of every operation above, built from the same schemas the API serves with. See OpenAPI.