API Explorer

Every endpoint on api.weather.gov, grouped and explained for people who don’t already speak NWS — what it returns, who wants it, and a worked example you can run.

Built from the live OpenAPI spec (version 3.11.0) on 2026-08-22. New here? Start with how it thinks.

69 endpoints shown

Start Here

Almost every question that begins with a latitude and longitude starts at one of these. They translate a location into the identifiers the rest of the API speaks.

GET https://api.weather.gov/points/{latitude},{longitude}

Give it a latitude and longitude and it tells you everything the API needs to know about that spot: which of the 122 local forecast offices covers it, which square of that office’s forecast grid it falls in, which forecast zone and county it belongs to, and which radar watches it. Nearly every other endpoint wants one of those identifiers, so this is where the chain starts.

Anyone building an app that starts from “where the user is”. If you have coordinates and want a forecast, you call this first.

Worked example

https://api.weather.gov/points/39.7456,-97.0892

A spot in Washington County, Kansas. The response points at grid TOP/32,81 — feed that into the gridpoint forecast endpoint next.

Open on api.weather.gov

cURL

curl "https://api.weather.gov/points/39.7456,-97.0892" \
  -H "User-Agent: (myweatherapp.example.com, me@example.com)"

GET https://api.weather.gov/points/{latitude},{longitude}/radio

Which NOAA Weather Radio transmitters cover a given point, so you know what frequency to tune an emergency radio to.

Emergency managers and preparedness sites telling people which channel to program.

Worked example

https://api.weather.gov/points/39.7456,-97.0892/radio

Open on api.weather.gov

cURL

curl "https://api.weather.gov/points/39.7456,-97.0892/radio" \
  -H "User-Agent: (myweatherapp.example.com, me@example.com)"

GET https://api.weather.gov/points/{latitude},{longitude}/stations

The observation stations nearest a given latitude and longitude, closest first. Handy when you want “what is it doing right now near me” rather than a forecast.

App developers who need a current-conditions station for an arbitrary point.

Worked example

https://api.weather.gov/points/39.7456,-97.0892/stations

Open on api.weather.gov

cURL

curl "https://api.weather.gov/points/39.7456,-97.0892/stations" \
  -H "User-Agent: (myweatherapp.example.com, me@example.com)"