NOAA Weather Alerts Scraper API - NWS Severe Warnings avatar

NOAA Weather Alerts Scraper API - NWS Severe Warnings

Pricing

from $1.60 / 1,000 nws active weather alerts scraper api evidence items

Go to Apify Store
NOAA Weather Alerts Scraper API - NWS Severe Warnings

NOAA Weather Alerts Scraper API - NWS Severe Warnings

Search the National Weather Service active-alert GeoJSON API by area, point, zone, region, event and warning attributes. Returns bounded source-linked warning evidence, timing, instructions, geocodes and geometry with explicit no-match and source outcomes.

Pricing

from $1.60 / 1,000 nws active weather alerts scraper api evidence items

Rating

0.0

(0)

Developer

Ava Torres

Ava Torres

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

11 days ago

Last modified

Features

Limited permissions

Share

NWS Active Weather Alerts Scraper API

Search the official National Weather Service active-alert GeoJSON endpoint by state/area, point, NWS zone, or region. Filter warning evidence by event, urgency, severity, certainty, status, message type, and RFC3339 overlap window.

Fast default

{"area":"CA","maxResults":3}

This preserves NWS order and returns up to three active California alerts, or one explicit NO_MATCH record. At $0.0001/start + $0.002/item, the default costs at most $0.0061.

Official endpoint:

$curl -H 'User-Agent: your-app/1.0 (you@example.com)' -H 'Accept: application/geo+json' 'https://api.weather.gov/alerts/active?area=CA'

FOUND rows normalize alert ID, event, headline, description, instruction, area and affected zones, timestamps, severity/certainty/urgency, sender, response type, geocode, geometry, source URL, retrieval time, and NWS update metadata. Invalid input, no match, and exhausted source retries are distinct explicit outcomes.

Important safety limits

Alerts are dynamic NWS-issued public warning evidence—not a complete historical archive, forecast, guaranteed delivery service, localized safety determination, or substitute for emergency instructions. Geometry and area descriptions may be broad; alerts may be updated, replaced, or cancelled. Always check current weather.gov/local emergency channels and follow official safety instructions.

See the full README for all fields, examples, filters, and time semantics.

How to use

  1. Open NOAA Weather Alerts Scraper API - NWS Severe Warnings in Apify Console and click Start (or Try for free).
  2. Fill in the input form - start with State / area code, Maximum results. Every field is optional unless marked required, and the form is prefilled with a working example.
  3. Set Maximum results to cap your cost, then run the Actor.
  4. Download the results as JSON, CSV, Excel, XML or HTML, or pull them with the Apify API.

Input

FieldTypeRequiredDefaultDescription
areastringno"CA"Two-letter state or territory code, such as CA.
pointstringnoLatitude,longitude. Clear area before using.
zonestringnoNWS zone code such as CAZ041. Clear area before using.
regionstringnoNWS region code. Clear area before using.
eventstringnoExact case-insensitive event name, such as Heat Advisory.
urgencystringnoExact NWS urgency value.
severitystringnoExact NWS severity value.
certaintystringnoExact NWS certainty value.
statusstringnoExact status, normally Actual.
messageTypestringnoExact message type such as Alert, Update, or Cancel.
startTimestringnoRFC3339 time. Includes alerts whose reported interval overlaps the window.
endTimestringnoRFC3339 time; must not precede startTime.
maxResultsintegerno3Total paid-item cap. Default 3 costs at most $0.0061 including start.

Example input

{
"area": "CA",
"maxResults": 3
}

Output example

One record from a real run (long values shortened, contact details partly masked):

{
"outcome": "FOUND",
"alertId": "urn:oid:2.49.0.1.840.0.7b0334871444cd88d73f14a0b68983da4d942905.001.1",
"event": "Dense Fog Advisory",
"headline": "Dense Fog Advisory issued November 11 at 9:59AM PST until November 11 at 10:00AM PST by NWS San Francisco CA",
"description": "Visibilities across the region continue to improve. Thus, the Dense\nFog Advisory will be allowed to expire at 10 AM PST.",
"instruction": "",
"areaDescription": "San Francisco; North Bay Interior Valleys; San Francisco Bay Shoreline",
"affectedZones": [
"https://api.weather.gov/zones/forecast/CAZ006",
"https://api.weather.gov/zones/forecast/CAZ506",
"https://api.weather.gov/zones/forecast/CAZ508"
],
"effective": "2026-11-11T09:59:00-08:00",
"onset": "2026-11-11T09:59:00-08:00",
"expires": "2026-11-11T11:00:00-08:00",
"ends": "2026-11-11T10:00:00-08:00",
"sent": "2026-11-11T09:59:00-08:00",
"status": "Actual",
"messageType": "Alert",
"category": "Met",
"severity": "Moderate",
"certainty": "Likely",
"urgency": "Expected",
"sender": "w***@noaa.gov",
"senderName": "NWS San Francisco CA",
"responseType": "Execute",
"geocode": {
"SAME": [
"006075",
"006041",
"006055"
],
"UGC": [
"CAZ006",
"CAZ506",
"CAZ508"
]
},
"geometry": null,
"sourceUrl": "https://api.weather.gov/alerts/active?area=CA"
}

Pricing

Pay per event: $0.002 per nws active weather alerts scraper api evidence item plus $0.0001 per run start. No subscription to this Actor is needed. Apify Store discounts apply, so the price per result is lower on Silver, Gold and higher Apify plans. Use Maximum results to cap the cost of each run.

FAQ

How much does NOAA Weather Alerts Scraper API - NWS Severe Warnings cost?

$0.002 per nws active weather alerts scraper api evidence item plus $0.0001 per run. For example, 1,000 results cost about $2.00. Higher Apify plans get a Store discount.

Do I need an API key or login?

No. Just configure the input and run it.

Can I run it on a schedule or from code?

Yes. Use Apify Schedules for recurring runs, or call it from the Apify API, the JavaScript or Python client, Make, Zapier, n8n, or any MCP-compatible AI agent.

Why did my run return no results?

Your filters are probably too narrow. Remove a filter or broaden the search, then run again. You only pay the result price for records that are actually saved.

Is the data accurate and up to date?

Each run fetches live data from the source described above, so results are as current as that source. Verify critical records with the original source before acting on them.