Logistics platform · route optimisation
Postcode intelligence for delivery routing
The problem
Routing engines want a stable per-postcode shape: lat/lng, LSOA, region, parliamentary constituency. postcodes.io has all of this but every routing platform integrates it from scratch. Worse: the routing engine then ALSO wants crime data for driver-safety routing, flood data for flood-season detours, and a stable schema to map both onto.
How Stratum fits
One endpoint returns geography (lat/lng, LSOA, admin district, constituency) + crime trend + flood + EPC-density + IMD (when wired) + connectivity (broadband / mobile / PTAL — roadmap). Stable JSON shape across the eight sources. Bulk endpoint accepts up to 100 postcodes per call; volume bands cut the per-postcode cost to fractions of a penny at the largest tier. Daily-refresh crons keep crime + flood data current without your team building a refresh pipeline.
One request
# Request
curl -X POST https://api.stratumapis.com/v1/postcode/bulk -H "x-stratum-key: $KEY" -d '{"postcodes":["SW1A 1AA","M1 1AA","EH1 1AA"]}'
# Response
{ "results": [{"postcode": "SW1A 1AA", "found": true, "data": {...}}, ...], "count": 3 }Set $KEY from your dashboard.
Frequently asked
Are bulk lookups cheaper per postcode?
Yes. Volume bands match the single-check tiers (1, 10, 100, 1000-pack discounts). At 1000-pack tier the per-postcode cost is roughly a third of the single-check rate.
Does this include connectivity (broadband / mobile)?
Roadmap. The Ofcom Connected Nations dataset is on the next-quarter list. Until then, postcodes.io's geography + Police.uk's crime + EA's flood are the three live capabilities.
How do you handle invalid postcodes?
We pre-validate against the UK postcode regex; obvious malformations 400 immediately. Postcodes that look valid but postcodes.io can't resolve return a 404 with a friendly hint.