Developer Reference
HailScore API
REST API for property-level hail verification, scoring, and event history. Every event in every response is cited from its originating publisher with the publisher's native record identifier. Bearer-token authentication; per-key rate limiting.
Authentication
All /v1/property/* endpoints require an API key passed via the Authorization header. Meta endpoints (/v1/meta/*) are unauthenticated and may be polled freely.
Authorization: Bearer hs_live_<your-key>
Keys are issued on request. Pilot keys carry per-minute and per-day rate limits scoped to the engagement tier (see /for-carriers for tier definitions). To request a key, email pilots@myhailscore.com.
Quickstart
§II.1 · Verify a date of loss
curl "https://www.myhailscore.com/v1/property/verify" \ -H "Authorization: Bearer hs_live_••••••••" \ --data-urlencode "address=1847 Elmwood Drive, Aurora, CO 80012" \ --data-urlencode "date_of_loss=2024-06-19" \ -G
§II.2 · Score a property
curl "https://www.myhailscore.com/v1/property/score" \ -H "Authorization: Bearer hs_live_••••••••" \ --data-urlencode "address=1847 Elmwood Drive, Aurora, CO 80012" \ --data-urlencode "roof_age=12" \ --data-urlencode "roof_type=asphalt_shingle" \ -G
§II.3 · Pull full event history
curl "https://www.myhailscore.com/v1/property/history" \ -H "Authorization: Bearer hs_live_••••••••" \ --data-urlencode "address=1847 Elmwood Drive, Aurora, CO 80012" \ --data-urlencode "since=2015-01-01" \ -G
§II.4 · Check methodology version
curl "https://www.myhailscore.com/v1/meta/methodology"
Endpoints
/v1/property/verifyDate-of-loss verification. Returns hail events within a window around the loss date, each cited from its publisher.
/v1/property/scoreCalibrated HailScore (0–100) for a property, with cited events that produced the score.
/v1/property/historyFull chronological event history. Useful for portfolio sweeps and SIU pattern review.
/v1/meta/methodologyMethodology version, last-updated date, and changelog. No auth required.
/v1/meta/healthService health and per-feed data freshness. No auth required.
Source citations
Every event in every response carries a sources array. Each entry names the originating publisher and the publisher's native record identifier so the receiving party can verify every fact against the public-record source.
"sources": [
{ "publisher": "NOAA_SED",
"record_id": "174532-1056981",
"url": "https://www.ncdc.noaa.gov/stormevents/eventdetails.jsp?id=1056981" },
{ "publisher": "NEXRAD_SWDI",
"record_id": "KFTG/2024-06-19T21:47:00.000Z",
"detail": { "station": "KFTG", "timestamp": "2024-06-19T21:47:00.000Z" } },
{ "publisher": "MRMS_MESH",
"record_id": "MESH-MAX-1440min/2024-06-19T21:47:00.000Z",
"detail": { "product": "MESH-MAX-1440min", "timestamp": "2024-06-19T21:47:00.000Z" } }
]API access
Keys are issued on request, scoped to the engagement tier.
Pricing and tier definitions live on /for-carriers. For a 90-day pilot or production access, email the founder directly.