US Weather Alerts API - Active NWS Severe Storm Warnings
Pricing
$8.00 / 1,000 alerts
US Weather Alerts API - Active NWS Severe Storm Warnings
Active severe weather alerts, warnings and watches from NOAA / the US National Weather Service. Filter by state, coordinates, severity or event type. When an area has no active alerts it says so in a row you can read, instead of returning nothing and leaving you to guess.
Pricing
$8.00 / 1,000 alerts
Rating
0.0
(0)
Developer
NeverEmpty
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
13 hours ago
Last modified
Categories
Share
Active severe weather alerts from the US National Weather Service, straight from api.weather.gov. No scraping, no HTML parsing, no browser.
Ask for the whole country, a state, or a single point on the map. Filter by severity, urgency, or event name.
What you get
One row per active alert:
| Field | |
|---|---|
event | Tornado Warning, Heat Advisory, Flood Watch, … as NWS names it |
severity | Extreme / Severe / Moderate / Minor / Unknown |
urgency | Immediate / Expected / Future / Past / Unknown |
certainty | Observed / Likely / Possible / Unlikely / Unknown |
headline / description / instruction | the text NWS issued, unedited |
areaDesc | the counties and zones the alert covers |
onset / expires / ends / effective / sent | ISO timestamps |
senderName | which NWS office issued it |
status / messageType / category / response | the CAP fields |
alertId / web | the alert's identifier and its page |
scope / scopeKind / checkedAt | which input produced this row, and when |
"No alerts" is an answer, not an error
Most of the time, most places have nothing active. When that happens this Actor writes a row saying so:
{ "scope": "VT", "ok": true, "alertCount": 0,"note": "No active alerts for this area right now. This is a valid result, not an error.","checkedAt": "2026-08-30T08:00:00.000Z" }
That row is not charged. It exists so that a scheduled run which finds nothing is distinguishable from a run that failed — which matters a lot when you are alerting off this data and silence is ambiguous.
Likewise, an input that cannot be read ("Tokyo", "ZZ") produces a row explaining exactly that, and no request is sent to NWS.
Input
{"areas": ["US", "CA", "TX", "38.89,-77.03"],"severity": ["Extreme", "Severe"],"urgency": [],"event": [],"maxRetries": 3}
| Input | |
|---|---|
areas | US for nationwide, a two-letter state or territory code (CA, TX, PR, GU), or "lat,lon". Mix them. |
severity | Keep only these. Empty = all. |
urgency | Keep only these. Empty = all. |
event | Keep only these event names, spelled as NWS spells them. Empty = all. |
maxRetries | Retries when NWS rate-limits or has an outage. |
Measured on 2026-08-30: US returned 269 active alerts, CA 4, TX 2, and a point in Washington DC 0.
Billing
Charged per alert delivered. Rows that report zero alerts, and rows that explain a bad input or an outage, are free. If you set a maximum total charge on the run and it is reached, the run stops and says so in the log and the run status rather than handing you a partial result that looks complete.
Source and conduct
Data comes from the National Weather Service public API. NWS states that the information is "open data, free to use for any purpose" and asks that clients identify themselves with a User-Agent; this Actor sends one that includes a contact URL, so NWS can reach us rather than block us if anything ever looks wrong.