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
Radar
Metadata about the NEXRAD radar network: where the radars are, whether they are healthy, and how their data is flowing.
Data from a wind profiler — a radar that points straight up and measures wind at many heights continuously, filling gaps between twice-daily balloon launches.
Aviation meteorologists and researchers studying the boundary layer.
2 parameters
Name
In
Required
Notes
time
query
no
Time interval
interval
query
no
Averaging interval
GEThttps://api.weather.gov/radar/queues/{host}
The processing queue for a radar host — how much data is backed up waiting to be handled.
Anyone diagnosing radar data lag.
8 parameters
Name
In
Required
Notes
limit
query
no
Record limit
integer
arrived
query
no
Range for arrival time
created
query
no
Range for creation time
published
query
no
Range for publish time
station
query
no
Station identifier
string
type
query
no
Record type
string
feed
query
no
Originating product feed
string
resolution
query
no
Resolution version
integer
GEThttps://api.weather.gov/radar/servers
Health of the servers that collect and distribute radar data. Deeply internal, and interesting precisely because it is normally invisible.
Infrastructure watchers and anyone investigating a radar data outage.
Every radar site NWS operates, with location and station type. This is the NEXRAD network — the roughly 160 big dishes whose data becomes the radar loop you see on TV.
Anyone mapping radar coverage or building a radar site picker.
3 parameters
Name
In
Required
Notes
stationType
query
no
Limit results to a specific station type or types
array
reportingHost
query
no
Show RDA and latency info from specific reporting host
string