NWS Weather Alerts Fetcher
Pricing
Pay per usage
NWS Weather Alerts Fetcher
Fetches active weather alerts (watches, warnings, advisories) from the official U.S. National Weather Service (NOAA) for a geographic zone, county AREA, or lat/lon coordinates — no API key required.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Bruno Finger
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Fetches active weather alerts (watches, warnings, and advisories) from the official U.S. National Weather Service (NOAA) for any NWS forecast zone, county AREA, or lat/lon coordinates — completely no API key required.
Sourced from the National Weather Service API (api.weather.gov).
Input
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
locations | array[string] | yes | — | List of NWS forecast-zone codes (e.g. "NCZ051"), AREA/county codes (e.g. "NCC183"), or lat/lon pairs (e.g. "35.779,-78.638"). For coordinates, the forecast zone is resolved automatically via the NWS /points endpoint. Maximum 100. |
includeSummary | boolean | no | true | If true, also emit one summary record per location listing all alerts found. |
timeoutSeconds | integer | no | 30 | HTTP timeout per NWS API request (1–120). |
Input examples
Zone code:
{"locations": ["NCZ051"],"includeSummary": true}
Lat/lon coordinates (auto-resolves zone):
{"locations": ["35.779,-78.638"],"includeSummary": true}
AREA / county code:
{"locations": ["NCC183", "NCZ051"],"timeoutSeconds": 45}
Output
One dataset item per alert (fields: type, severity, urgency, certainty, areas, description, instruction, onset, expires, sent, status, headline, link) plus a summary item per location (queryType, queryValue, zone, title, updated, alertCount, alerts, resolvedLocation). Failed lookups emit an item with an error field.
The overview dataset view shows queryType, queryValue, zone, title, updated, alertCount, and error.
Usage
cd nws-weather-alerts-fetcherpython3 -m venv .venv.venv/bin/pip install -r requirements.txtecho '{"locations": ["NCZ051"], "includeSummary": true}' > INPUT.json.venv/bin/python src/main.py
Or with the Apify CLI:
$apify run --input-file INPUT.json
Pricing
PAY_PER_EVENT — $0.001 per alerts-fetched event (one zone/query).
Notes
- The NWS API is keyless (no registration needed for the alerts endpoint).
- Zone codes: forecast zones look like
NCZ041,TXC491,MAC025. AREA (county) codes look likeNCC183. - Lat/lon coordinates are automatically resolved to a forecast zone via the
/pointsendpoint. - An empty
featuresarray means no active alerts (a valid result — not an error). - Rate limits: NWS requests a User-Agent with contact info and recommends no more than 1 requests/second.
- The
/pointsendpoint returns 404 for some international or off-shore coordinates; ensure coordinates are within the U.S.
Related actors
- Open-Meteo Weather — general weather forecasts (Open-Meteo API)
- Aviation Weather METAR/TAF — aviation observations and forecasts (NOAA Aviation Weather Center)