Check active tornado, storm, flood and winter weather warnings for any US location.
Weather Alerts returns the severe weather warnings, watches and advisories in effect right now for any point or state in the United States, straight from the National Weather Service. Each alert names the event, how severe and urgent it is, the area covered, when it starts and ends, and what to do.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"location": {
"state": "TX"
},
"count": 2,
"highestSeverity": "Severe",
"alerts": [
{
"id": "urn:oid:2.49.0.1.840.0.f9aca49ebcd46d4148ecadc4f42f00d6fee04ca6.001.1",
"event": "Flood Warning",
"headline": "Flood Warning issued October 2 at 1:51PM CDT until October 3 at 2:51AM CDT by NWS Fort Worth TX",
"summary": "FLOOD WARNING NOW IN EFFECT UNTIL LATE TONIGHT",
"severity": "Severe",
"urgency": "Immediate",
"certainty": "Observed",
"response": "Avoid",
"messageType": "Update",
"area": "Dallas, TX",
"issuedBy": "NWS Fort Worth TX",
"sent": "2026-10-02T13:51:00-05:00",
"onset": "2026-10-02T13:51:00-05:00",
"expires": "2026-10-03T03:00:00-05:00",
"ends": "2026-10-03T02:51:00-05:00",
"description": "...The Flood Warning continues for the following rivers in Texas...\n\nTrinity River At Dallas affecting Dallas County.\n\n* WHAT...Minor flooding is occurring and minor flooding is forecast.\n\n* WHERE...Trinity River at Dallas.\n\n* WHEN...Until late tonight.\n\n* IMPACTS...At 30.0 feet, Minor lowland flooding will begin, and\ntrails along the river begin to flood.\n\n* ADDITIONAL DETAILS...\n- At 1:30 PM CDT Friday the stage was 30.9 feet.\n- Forecast...The river is expected to fall below flood stage this\nafternoon and continue falling to 12.7 feet early Wednesday\nafternoon.\n- Bankfull stage is 30.0 feet.\n- Flood stage is 30.0 feet.",
"instruction": "Do not drive cars through flooded areas. Caution is urged when\nwalking near riverbanks.\n\nAdditional information is available at water.noaa.gov/wfo/fwd.",
"geometry": {
"type": "Polygon",
"coordinates": [
[
[
-96.93,
32.75
],
[
-96.93,
32.81
],
[
-96.83,
32.83
],
[
-96.71,
32.75
],
[
-96.76,
32.69
],
[
-96.87,
32.78
],
[
-96.93,
32.75
]
]
]
}
},
{
"id": "urn:oid:2.49.0.1.840.0.b7cdd851a493afa58b5cf5fc13948ba8a35d2b25.001.1",
"event": "Flood Watch",
"headline": "Flood Watch issued October 2 at 1:36AM CDT until October 2 at 7:00PM CDT by NWS Corpus Christi TX",
"summary": "FLOOD WATCH REMAINS IN EFFECT THROUGH THIS EVENING",
"severity": "Severe",
"urgency": "Future",
"certainty": "Possible",
"response": "Prepare",
"messageType": "Update",
"area": "La Salle; McMullen; Live Oak; Bee; Goliad; Victoria; Webb; Duval; Jim Wells; Inland Kleberg; Inland Nueces; Inland San Patricio",
"issuedBy": "NWS Corpus Christi TX",
"sent": "2026-10-02T01:36:00-05:00",
"onset": "2026-10-02T01:36:00-05:00",
"expires": "2026-10-02T19:00:00-05:00",
"ends": "2026-10-02T19:00:00-05:00",
"description": "* WHAT...Flooding caused by excessive rainfall continues to be\npossible.\n\n* WHERE...A portion of south Texas, including the following areas,\nBee, Duval, Goliad, Inland Kleberg, Inland Nueces, Inland San\nPatricio, Jim Wells, La Salle, Live Oak, McMullen, Victoria and\nWebb.\n\n* WHEN...Through this evening.\n\n* IMPACTS...Excessive runoff may result in flooding of rivers,\ncreeks, streams, and other low-lying and flood-prone locations.\nFlooding may occur in poor drainage and urban areas.\n\n* ADDITIONAL DETAILS...\n- Flooding caused by excessive rainfall is possible. Additional\nrainfall totals of 1-3 inches with isolated higher amounts will\nfall over areas that have already seen 2-4\" of rain within the\nwatch area.\n- http://www.weather.gov/safety/flood",
"instruction": "You should monitor later forecasts and be alert for possible Flood\nWarnings. Those living in areas prone to flooding should be prepared\nto take action should flooding develop.",
"geometry": null
}
]
}
}
About the Weather Alerts API
Send a latitude and longitude for the alerts covering one place, or a two-letter state code for everything in effect across the state. Every plan gets the event, severity, urgency, area, timing and safety instructions. Paid plans add the full forecaster description and the warning polygon as GeoJSON, ready to draw on a map.
What people use it for
- Field Crew Safety
- Dispatch and workforce apps check each job site for active tornado, lightning and flood warnings before sending crews out, and pull workers back when a warning is issued for their location.
- Event and Venue Operations
- Outdoor venues and event organizers watch for severe thunderstorm and high wind warnings at their exact location to trigger shelter plans and delays early.
- Logistics and Fleet Routing
- Fleet software checks warnings along delivery stops and depots to reroute around winter storms, flooding and dust storms before drivers reach them.
- Property and Home Monitoring
- Smart home and property management apps notify owners when a freeze, flood or hurricane warning covers a home so they can act before damage happens.
- Weather Apps and Widgets
- Weather apps draw storm-based warning polygons on their maps and show the most severe alert first, with the forecaster's own instructions.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Weather Alerts
Same data, same APIVerve account, same credit balance — one key works on all of them.
Which locations does Weather Alerts cover?
Does a point lookup return alerts for the whole county?
How current are the alerts?
How far does the Starter plan go for alert checks?
What do paid plans add?
Can I show these alerts in a commercial app?
Request parameters — GET /v1/weatheralerts
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
latOptional | number | 38.627 | Latitude of the location to check. Send with lon range -90-90 |
lonOptional | number | -90.1994 | Longitude of the location to check. Send with lat range -180-180 |
stateOptional | string | TX | Two-letter US state or territory code (e.g., MO) for every alert in effect across it. Used when lat and lon are not sent |
curl "https://api.apiverve.com/v1/weatheralerts?lat=38.627&lon=-90.1994&state=TX" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/weatheralerts
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"location": {
"state": "TX"
},
"count": 2,
"highestSeverity": "Severe",
"alerts": [
{
"id": "urn:oid:2.49.0.1.840.0.f9aca49ebcd46d4148ecadc4f42f00d6fee04ca6.001.1",
"event": "Flood Warning",
"headline": "Flood Warning issued October 2 at 1:51PM CDT until October 3 at 2:51AM CDT by NWS Fort Worth TX",
"summary": "FLOOD WARNING NOW IN EFFECT UNTIL LATE TONIGHT",
"severity": "Severe",
"urgency": "Immediate",
"certainty": "Observed",
"response": "Avoid",
"messageType": "Update",
"area": "Dallas, TX",
"issuedBy": "NWS Fort Worth TX",
"sent": "2026-10-02T13:51:00-05:00",
"onset": "2026-10-02T13:51:00-05:00",
"expires": "2026-10-03T03:00:00-05:00",
"ends": "2026-10-03T02:51:00-05:00",
"description": "...The Flood Warning continues for the following rivers in Texas...\n\nTrinity River At Dallas affecting Dallas County.\n\n* WHAT...Minor flooding is occurring and minor flooding is forecast.\n\n* WHERE...Trinity River at Dallas.\n\n* WHEN...Until late tonight.\n\n* IMPACTS...At 30.0 feet, Minor lowland flooding will begin, and\ntrails along the river begin to flood.\n\n* ADDITIONAL DETAILS...\n- At 1:30 PM CDT Friday the stage was 30.9 feet.\n- Forecast...The river is expected to fall below flood stage this\nafternoon and continue falling to 12.7 feet early Wednesday\nafternoon.\n- Bankfull stage is 30.0 feet.\n- Flood stage is 30.0 feet.",
"instruction": "Do not drive cars through flooded areas. Caution is urged when\nwalking near riverbanks.\n\nAdditional information is available at water.noaa.gov/wfo/fwd.",
"geometry": {
"type": "Polygon",
"coordinates": [
[
[
-96.93,
32.75
],
[
-96.93,
32.81
],
[
-96.83,
32.83
],
[
-96.71,
32.75
],
[
-96.76,
32.69
],
[
-96.87,
32.78
],
[
-96.93,
32.75
]
]
]
}
},
{
"id": "urn:oid:2.49.0.1.840.0.b7cdd851a493afa58b5cf5fc13948ba8a35d2b25.001.1",
"event": "Flood Watch",
"headline": "Flood Watch issued October 2 at 1:36AM CDT until October 2 at 7:00PM CDT by NWS Corpus Christi TX",
"summary": "FLOOD WATCH REMAINS IN EFFECT THROUGH THIS EVENING",
"severity": "Severe",
"urgency": "Future",
"certainty": "Possible",
"response": "Prepare",
"messageType": "Update",
"area": "La Salle; McMullen; Live Oak; Bee; Goliad; Victoria; Webb; Duval; Jim Wells; Inland Kleberg; Inland Nueces; Inland San Patricio",
"issuedBy": "NWS Corpus Christi TX",
"sent": "2026-10-02T01:36:00-05:00",
"onset": "2026-10-02T01:36:00-05:00",
"expires": "2026-10-02T19:00:00-05:00",
"ends": "2026-10-02T19:00:00-05:00",
"description": "* WHAT...Flooding caused by excessive rainfall continues to be\npossible.\n\n* WHERE...A portion of south Texas, including the following areas,\nBee, Duval, Goliad, Inland Kleberg, Inland Nueces, Inland San\nPatricio, Jim Wells, La Salle, Live Oak, McMullen, Victoria and\nWebb.\n\n* WHEN...Through this evening.\n\n* IMPACTS...Excessive runoff may result in flooding of rivers,\ncreeks, streams, and other low-lying and flood-prone locations.\nFlooding may occur in poor drainage and urban areas.\n\n* ADDITIONAL DETAILS...\n- Flooding caused by excessive rainfall is possible. Additional\nrainfall totals of 1-3 inches with isolated higher amounts will\nfall over areas that have already seen 2-4\" of rain within the\nwatch area.\n- http://www.weather.gov/safety/flood",
"instruction": "You should monitor later forecasts and be alert for possible Flood\nWarnings. Those living in areas prone to flooding should be prepared\nto take action should flooding develop.",
"geometry": null
}
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
location | object | {...} | The location that was checked: lat and lon, or state |
state | string | "TX" | |
count | number | 2 | Number of alerts in effect |
highestSeverity | string | "Severe" | Severity of the most serious alert (Extreme, Severe, Moderate, Minor or Unknown), or null when there are none |
alerts | array[2] | Alerts in effect, most severe and most urgent first | |
id | string | "urn:oid:2.49.0.1.840.0.f9aca49ebcd46d4148ecadc4f42f00d6fee04ca6.001.1" | National Weather Service identifier for the alert |
event | string | "Flood Warning" | Kind of alert (e.g., Tornado Warning, Flood Watch, Wind Advisory) |
headline | string | "Flood Warning issued October 2 at 1:51PM CDT until October 3 at 2:51AM CDT by NWS Fort Worth TX" | One-line description of the alert with its issue and end times |
summary | string | "FLOOD WARNING NOW IN EFFECT UNTIL LATE TONIGHT" | The forecaster's short headline for the alert, or null when none was given |
severity | string | "Severe" | Extreme, Severe, Moderate, Minor or Unknown |
urgency | string | "Immediate" | Immediate, Expected, Future, Past or Unknown |
certainty | string | "Observed" | Observed, Likely, Possible, Unlikely or Unknown |
response | string | "Avoid" | Recommended action type (e.g., Shelter, Evacuate, Prepare, Avoid, Monitor) |
messageType | string | "Update" | Alert for a new alert, Update for a revised one |
area | string | "Dallas, TX" | Counties or zones the alert covers |
issuedBy | string | "NWS Fort Worth TX" | National Weather Service office that issued the alert |
sent | string | "2026-10-02T13:51:00-05:00" | When the alert was sent, as an ISO 8601 timestamp |
onset | string | "2026-10-02T13:51:00-05:00" | When the hazard is expected to begin, as an ISO 8601 timestamp |
expires | string | "2026-10-03T03:00:00-05:00" | When this message expires, as an ISO 8601 timestamp |
ends | string | "2026-10-03T02:51:00-05:00" | When the hazard is expected to end, as an ISO 8601 timestamp, or null |
descriptionPremium | string | "...The Flood Warning continues for the following rivers in Texas...
Trinity River At Dallas affecting Dallas County.
* WHAT...Minor flood… | The forecaster's full description of the hazard, where and when |
instruction | string | "Do not drive cars through flooded areas. Caution is urged when
walking near riverbanks.
Additional information is available at water.noaa.… | What to do, in the forecaster's words, or null |
geometryPremium | object | {...} | GeoJSON polygon of a storm-based warning, or null for alerts that cover whole zones |
typePremium | string | "Polygon" | |
coordinatesPremium | array | Array of arrays |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 5 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Weather Alerts calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 40 | Free |
| Starter | $29.99 | 200,000 | 40,000 | $0.75 |
| Pro | $99.99 | 1,000,000 | 200,000 | $0.50 |
| Mega | $299.99 | 4,000,000 | 800,000 | $0.37 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/weatheralerts
No SDK to install — this is a plain HTTPS call to /v1/weatheralerts with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/weatheralerts" \
-H "x-api-key: YOUR_API_KEY"Resources
Call it from Node.js — GET /v1/weatheralerts
No SDK to install — this is a plain HTTPS call to /v1/weatheralerts with your key in the x-api-key header. Swap in a real key and it runs as-is.
const res = await fetch("https://api.apiverve.com/v1/weatheralerts", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Call it from Python — GET /v1/weatheralerts
No SDK to install — this is a plain HTTPS call to /v1/weatheralerts with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/weatheralerts",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Call it from C# / .NET — GET /v1/weatheralerts
No SDK to install — this is a plain HTTPS call to /v1/weatheralerts with your key in the x-api-key header. Swap in a real key and it runs as-is.
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/weatheralerts");
Console.WriteLine(json);Resources
Call it from Go — GET /v1/weatheralerts
No SDK to install — this is a plain HTTPS call to /v1/weatheralerts with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/weatheralerts", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Call it from PHP — GET /v1/weatheralerts
No SDK to install — this is a plain HTTPS call to /v1/weatheralerts with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/weatheralerts");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Call it from Ruby — GET /v1/weatheralerts
No SDK to install — this is a plain HTTPS call to /v1/weatheralerts with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/weatheralerts")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Zero-code embed — one snippet, no backend
Drop an interactive Weather Alerts form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Weather Alerts API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Weather Alerts API.
Weather
- Air Quality
- Marine Weather
- Moonrise Moonset
- Solar Potential
- Sunrise Sunset
- Weather
- Weather Alerts
- Weather Seasons
- Worldwide Earthquakes