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.
Free storm history for any US address
Stormwatch for developers
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.Available hail, wind, heavy-rain and flood records at a point. Selected hail and wind thresholds travel with the response. Source gaps stay visible.
Bounded historical hail contours and NWS wind or flood-warning areas. Warning polygons and radar estimates keep their own meaning.
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.
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 →Start with a property record
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.
| Operation | Endpoint | Key scope |
|---|---|---|
| Point storm history | POST /api/v1/history | history:read |
| Local historical map layer | POST /api/v1/map/layers | maps:read |
| Existing town weather | GET /api/v1/weather/{state}/{town} | weather:read |
Simple by design
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.