Stormwatch.

Free storm history for any US address

Stormwatch for developers

Put a clearer storm picture
inside your software.

Free storm-history data, map layers and public town weather. One useful connection for the people who already count on your platform.

Starting with an approved partner pilot. Contact us with your company, product website and expected use.
01 / Storm history

Evidence, with its context.

Available hail, wind, heavy-rain and flood records at a point. Selected hail and wind thresholds travel with the response. Source gaps stay visible.

02 / Map layers

A storm story on the map.

Bounded historical hail contours and NWS wind or flood-warning areas. Warning polygons and radar estimates keep their own meaning.

03 / Weather embeds

Local weather, easy to add.

Public town radar and dated forecast views inside an approved website. A clear Powered by Stormwatch link brings people back to the source.

A small integration. A useful addition.

Built for your backend.
Friendly to your customers.

  1. Tell us what you’re building. We review your use, web domains and expected traffic.
  2. Connect with a scoped API key. Your backend requests the weather data it needs. Keys expire, rotate and can be revoked.
  3. Keep the source visible. Show Powered by Stormwatch with a link, source dates, coverage and the relevant limits.

Customers do not need to join Property Watcher to see weather inside your product. Partner access does not grant homeowner account data or permission to enroll or contact anyone.

Download the versioned OpenAPI specification →

Download the Node integration example → · Example license

Start with a property record

One request. A dated answer.

Send this from your server. Keep the key in your server’s secret store.

POST https://mystormwatch.com/api/v1/history
Authorization: Bearer YOUR_SERVER_SIDE_KEY
Content-Type: application/json

{"lat": 39.765, "lon": -86.165,
 "hail_min": 0.75, "wind_min": 60}

The example point is the public Indiana Statehouse. Requests use a JSON body so property coordinates and keys do not go in request URLs.

OperationEndpointKey scope
Point storm historyPOST /api/v1/historyhistory:read
Local historical map layerPOST /api/v1/map/layersmaps:read
Existing town weatherGET /api/v1/weather/{state}/{town}weather:read

Simple by design

Free access, with sensible limits.

The initial pilot allows up to 30 requests per minute and 1,000 per UTC day per partner, shared across that partner’s keys. Keys last at most 90 days. A busy service may return a retryable response; these limits are an initial pilot allowance, not a promise of national capacity or an uptime SLA.

Keep keys out of browser bundles, mobile apps, iframe markup and URLs. Public town embeds use an assigned, non-secret partner name and exact approved HTTPS domains. They read prepared weather; embedding does not start a clip-rendering job.

The hosted service is a free partner pilot. Public documentation and integration examples do not mean the full platform or data archive is released under an open-source license.

Use methodology, data sources and limits alongside your display. This information is not an inspection, damage determination or emergency warning service.