NOAA Weather Forecast & Alerts

What this Actor scrapes

Given a batch of up to 25 US latitude/longitude coordinates, this Actor calls NOAA/NWS's free api.weather.gov API to resolve each point's forecast grid, pull its 7-day forecast (plus an optional bounded hourly forecast), and check for currently active weather alerts — then joins all three into one dataset row per location. api.weather.gov needs no API key, but getting a usable answer means three to four separate calls per point, correct handling of out-of-coverage coordinates, and capping the ~156-period hourly payload yourself. This Actor does that plumbing so you get a ready-to-use row instead of a stack of raw NWS JSON to reconcile.

What we handle for you

• 🔗 We do the three-call join for you — grid resolution, forecast, and active alerts stitched into one row per coordinate, no NWS grid math required on your end.
• 🔁 We retry on 408 / 429 / 503 and network errors — exponential backoff up to 5 attempts, honouring Retry-After.
• 🌐 Apify Proxy rotation on every request — standard hygiene, fresh session per call.
• 🧭 Out-of-coverage coordinates are handled gracefully — a location outside NWS coverage is skipped with a clear status message, never a failed run.
• 🧊 Clean, typed dataset rows — Pydantic-validated, ISO-8601 timestamps, ready for JSON, CSV, or Excel export.
• 💰 Pay-Per-Event pricing — you only pay for locations that actually resolved. No data, no charge.

Use cases

• Logistics and routing — pull multi-stop forecasts and active alerts before dispatching a route.
• Agriculture — check 7-day and hourly forecasts across multiple fields in one run.
• Insurance risk — screen a portfolio of property coordinates for active severe-weather alerts.
• Events and venue planning — confirm forecast and alert status for outdoor event locations.
• Energy-demand forecasting — feed grid-level temperature and forecast data into a demand model.

Input

Paste this into the Apify Console, or send it as the run input over the API. Proxy settings are on by default; you rarely need to touch them.

{
  "coordinates": [
    "39.7456,-97.0892",
    "40.7128,-74.0060",
    "34.0522,-118.2437"
  ],
  "include_hourly_forecast": false
}

Output

One row per result, schema-validated before it is written. Export JSON, CSV, Excel or XML from the run, or read it over the API.

latitudelongitudegrid_idcitystateforecast_periodsactive_alertsalert_countretrieved_at

{
  "latitude": 39.7456,
  "longitude": -97.0892,
  "grid_id": "TOP",
  "grid_x": 31,
  "grid_y": 80,
  "city": "Concordia",
  "state": "KS",
  "forecast_periods": [
    {
      "name": "Overnight",
      "start_time": "2026-09-03T21:00:00-05:00",
      "end_time": "2026-09-04T06:00:00-05:00",
      "is_daytime": false,
      "temperature": 68,
      "temperature_unit": "F",
      "precipitation_probability": 20,
      "wind_speed": "10 mph",
      "wind_direction": "S",
      "short_forecast": "Partly Cloudy",
      "detailed_forecast": "Partly cloudy, with a low around 68."
    }
  ],
  "hourly_periods": [],
  "active_alerts": [],
  "alert_count": 0,
  "retrieved_at": "2026-09-03T14:32:10Z"
}

Pricing

You pay only for results that land. Cap any run with maxTotalChargeUsd. See pricing & billing for worked examples.

Limitations

• US/NWS coverage only — no international forecasts.
• Forecast and active alerts only — no historical or archival weather data.
• No built-in geocoding — supply raw lat,lon coordinates; geocode addresses or ZIPs upstream.
• Up to 25 coordinates per run — batch across multiple runs for larger coordinate lists.
• Hourly forecast is opt-in and capped at 156 periods to bound payload size.