Property Hazard Data API - Wildfire, Flood, Hail Risk

Ask what could happen to a property, one US street address at a time, from the hazard models insurers actually underwrite on.

What it collects

• Wildfire: risk scores in detailed, abbreviated and expanded forms, with or without special hazard zones, plus Firewise community status and the California brush fire report.
• Water: flood zone determination in guaranteed and non-guaranteed forms, hurricane catastrophe hazard, distance to coast and actual distance to coast, windpool eligibility, and lava and tsunami zones.
• Storm and ground: hail risk score, hail damage score, sinkhole risk and the California Department of Insurance earthquake zone.
• Fire protection: public protection class in detailed and abbreviated forms and its future effective version, which is the 1 to 10 grade for how well the local fire service could actually respond, plus the building code effectiveness grading schedule for the jurisdiction.
• Crime: the abbreviated crime risk report for the location.
• Territory and placement: property and auto rating territories, Citizens territory, premium tax jurisdiction, latitude and longitude, and a geocode accuracy check.
• Property and homeowner data: the property characteristics and owner data the provider holds for US residences, plus the UK replacement valuation and the Hong Kong property report.

FAQ

What is property hazard data used for?

Pricing and placing risk. An insurer needs the wildfire score, flood zone and fire protection class before it can quote; a lender needs the flood determination before it can close; a real estate investor wants to know what the hazard picture is before it shows up in the premium. All of it is keyed on the street address rather than on a parcel identifier, which is why it fits into workflows that only ever have an address.

Which hazards are covered?

Wildfire, flood, hurricane, hail, earthquake, sinkhole, lava and tsunami, brush fire, crime and coastal exposure, plus the two ratings that describe how well a place is defended rather than how exposed it is: the public protection class for the fire service, and the building code effectiveness grading schedule for the local code regime.

What is a public protection class?

A grade from 1 to 10 for the fire suppression capability covering a location, where 1 is exemplary and 10 means the area does not meet the programme's minimum criteria. It is one of the strongest single predictors of a property insurance rate in the US. This actor passes the grade through exactly as the provider publishes it, never rescaled or inverted, because the hazard scores in the same dataset run the other way and quietly flipping one to match the other would be worse than leaving both alone.

How do I give it an address?

One per line, as street, city, state and optionally postcode, separated by commas: 1 Main St, Austin, TX, 78703. The state has to be its two-letter code. A line without one is refused rather than sent, because this API answers on whatever it is given, and a report for an address it had to guess at would look exactly like a real answer.

Can I run a whole list of addresses?

Yes, and the actor paces it for you. This API takes one address per request with no batch form, so a long list is a long series of calls; the requests-per-minute setting is there because your contract may cap throughput, and the maximum results setting is there because every row is a separately metered lookup on your own provider account.

Which fields come back?

Whatever the provider publishes for that report, unchanged. The provider does not publish its response schemas openly, directing customers to their account manager for them, so this actor invents no field names: the whole answer travels on the row under reportData, and only the address echoed back and the status code the provider documents are lifted into their own columns. That way a field the provider adds tomorrow arrives without an actor change, and no column here is a guess.

What is the difference between the test and production gateways?

They are separate environments with separate credentials and separate data. The customer integration gateway is for building against; production is the real thing. Tick the test environment box to point at the former. A production key will be refused there and the other way round, which is the single most common reason a correct-looking credential does not work.

Why does it ask for an organisation id and a shipping id?

Because this API carries them inside every request body rather than as HTTP headers, and it will not answer without them. Your provider issues both alongside your credentials. They identify the account a lookup is billed to, which is separate from the credentials that prove who you are.

Do I need my own API key?

Yes. This actor is bring-your-own-key and never ships credentials of its own. Paste the consumer key and secret from your provider account, or set the key as the DATA_API_KEY environment secret. The pair is exchanged for a bearer token that the provider documents as lasting 60 minutes, so one exchange serves a whole run.

Why did a refusal not tell me whether my key was wrong?

Because it cannot be known from the outside. This gateway checks the credential before it looks at the path, so a refused token and an unknown route come back identically. Rather than assert one of them, the actor names both possibilities: if the same credentials work on another report, the problem is the request rather than the key.

What does it cost?

Pay per result. A hazard or property report costs the most, because each is a full model output for one address; a territory, tax or geocode answer costs well under half that, because placing an address is what you do before deciding whether to spend anything on the risk data about it. Platform usage is included. Addresses the provider has no report for are never charged.

Example output

{
  "recordType": "report",
  "report": "publicProtectionClassDetail",
  "reportLabel": "Public protection class, detailed",
  "requested": "1 Main St, Austin, TX, 78703",
  "found": true,
  "street": "1 Main St",
  "city": "Austin",
  "state": "TX",
  "zip": "78703",
  "environment": "production",
  "statusCode": 200,
  "reportData": { "...": "every field the provider published for this report, unchanged" }
}

Keyword map

property hazard data API, wildfire risk API, flood zone determination API, hail risk score, hurricane catastrophe hazard, earthquake zone lookup, sinkhole risk data, public protection class API, PPC fire protection grade, building code effectiveness grading, distance to coast API, windpool eligibility, crime risk by address, insurance underwriting data API, property risk score by address, homeowner data API, rating territory lookup, premium tax jurisdiction, geocode accuracy check, catastrophe risk data.