SStratum APIs

Insurer · home + contents pricing

Postcode intelligence for insurance quotes

The problem

Pricing home + contents at the postcode level needs a wider risk picture than crime alone. Flood + subsidence + coal mining + EPC band + index of multiple deprivation each shift the rate. The data sits in eight separate government feeds; integrating each one costs more developer-time than the line of business is worth.

How Stratum fits

The postcode-intelligence endpoint returns crime + flood + radon + coal mining + contaminated land + knotweed + EPC band + IMD decile in one response. All from free public-sector sources (postcodes.io / Police.uk / EA / Coal Authority / UKHSA / MHCLG / ONS) — no licence cost piling on the per-quote spend. Sub-200ms p95 on cached postcodes; ~600ms on cold pulls. Pair with the EPC endpoint for property-level MEES verdicts.

One request

# Request
curl "https://api.stratumapis.com/v1/postcode/SW1A%201AA" -H "x-stratum-key: $KEY"

# Response
{ "postcode": "SW1A 1AA", "localAuthority": "Westminster", "crime": {...}, "flood": {...}, "radon": {"band": "very-low"}, "coalMining": {"band": "none"}, "knotweed": {"band": "low"} }

Set $KEY from your dashboard.

Frequently asked

Does the response include EPC band?

EPC band lives on the EPC endpoint (`/v1/epc/postcode/{postcode}`) since EPCs are property-specific. Pair both endpoints for full property-level pricing.

How fresh is the crime data?

Police.uk publishes monthly. The endpoint returns the most recent month with a 12-month trend (W6 enrichment). Cached for 30 days per postcode to keep the call cost low.

Is flood data point-level or postcode-level?

Postcode-area resolution for the long-term band; live EA real-time monitoring station + warning at the property point. The full EA point-level Risk of Flooding from Rivers and Sea is on the roadmap.

Postcode Intelligence for Insurance Quotes | Stratum APIs