Location intelligence

Flood Risk API

Screen a property location in England, Wales or Scotland against flood zones, flood probability, recorded flood history, nearby defences, surface-water, reservoir and coastal erosion mapping. Use it as a flood risk data API inside your own property checks.

Flood risk API endpoint

GET/api/v1/property/flood-risk

Provide postcode, or both latitude and longitude.

Geographic availability

Coverage by UK nation

Green: supported Amber: partial Red: not supported

The colour is a geographic coverage indicator, not a risk score. Always inspect source status and completeness in the API response.

England

Supported

River, sea, surface water, defended probability, reservoirs, recorded outlines, defences and NCERM coastal mapping.

Wales

Partial

NRW flood zones, river, sea and surface-water risk, recorded flood extents, defences and NCERM erosion are configured. Reservoir and coastal ground-instability maps are not.

Scotland

Partial

SEPA river, coastal and surface-water likelihood maps are configured. Reservoir, erosion, recorded-history and defence data are not.

Northern Ireland

Not supported

DfI Rivers flood sources are not configured.

Cost per successful request

Pricing

A successful request costs 10 credits and checks the flood categories available for the property location.

API credits
10 credits

Deducted after a successful response.

Rejected or failed
No charge

Handler errors are not charged. A successful partial screen is charged.

What the API provides

River and sea flood zones

Checks EA Flood Zones 2 and 3 in England, NRW Flood Map for Planning zones in Wales, or the highest SEPA river and coastal likelihood band in Scotland, and normalises the result into a severity.

Defended flood probability

Returns the RoFRS band with minimum-depth layers in England, or the Flood Risk Assessment Wales high, medium or low band in Wales. Both take account of flood defences.

Surface-water mapping

Returns published risk bands and confidence values where the relevant source layer matches.

Reservoir scenarios

For England, checks dry-day and wet-day credible worst-case reservoir failure extents and returns available reservoir and lead-authority context.

Coastal erosion and instability

Checks NCERM erosion projections, with 2055 and 2105 horizons in England and 2025, 2055 and 2105 no active intervention zones in Wales. Coastal ground-instability zones are England only.

Recorded flood history

Checks whether the location intersects an Environment Agency Recorded Flood Outline or an NRW Recorded Flood Extent and returns available event dates, source and cause.

Nearby flood defences

Returns up to 25 EA or NRW defence assets inside the requested radius, with rounded distance. EA records add condition data; NRW records add the protection type and maintainer.

Ground height

Returns the height above mean sea level of the OS Terrain 50 cell (50 m) that contains the location, in metres to 0.1 m. Great Britain only.

Completeness

complete=false means at least one expected provider failed. Provider plumbing is deliberately excluded from the response.

Risk summary

Returns the highest normalised severity and matching category details.

Response guide

FieldMeaning
data.completeTrue only when every source expected for the resolved country answered successfully.
data.coverageResolved country, both England and Wales providers for coordinate-only input, or not-covered for Northern Ireland.
data.locationResolved property location and the radius used for nearby flood-defence checks.
data.riskLevelHighest normalised level: none, low, medium or high, or not_covered when the nation has no configured flood data.
data.risksEight fixed risk keys. Each contains riskLevel, count and a short details array. riskLevel is not_covered when no open source exists for that category in the nation.
data.elevationGround height in metres above mean sea level (metres), with source and resolutionMetres, from the 50 m OS Terrain 50 grid. null in Northern Ireland, outside Great Britain or when the lookup fails. It does not affect complete.

Useful request variants

Use canonical coordinates

curl -X GET "https://propertyinsights.co.uk/api/v1/property/flood-risk?latitude=52.123&longitude=-1.234" \
  -H "x-api-key: YOUR_API_KEY"

Use a wider defence search radius

curl -X GET "https://propertyinsights.co.uk/api/v1/property/flood-risk?postcode=ZZ1%201ZZ&radiusMetres=1000" \
  -H "x-api-key: YOUR_API_KEY"

Not included

  • Recorded Flood Outlines are known mapped records, not a complete incident or property-claims history.
  • Groundwater flooding and sewer flooding are not currently configured.
  • Elevation is the ground height of a 50 m grid cell, not the floor level of the building. Points at sea return the flat sea value near 0 m.
  • Reservoir and coastal ground-instability categories are England only and return not_covered in Wales. In Scotland only river, sea and surface water are checked; the other six categories return not_covered.
  • The result is not a Flood Risk Assessment, official search or statement of insurability.

Billing details in the response

Successful chargeable JSON responses include a top-level billing object. The endpoint examples on this page focus on the endpoint-specific data, so this repeated block may not be shown in every example.

"billing": {
  "mode": "prepaid",
  "creditsCharged": 1,
  "creditsRemaining": 1999,
  "creditsRefreshAt": "2026-08-14T09:30:00.000Z"
}
Field or headerMeaning
billing.creditsCharged
X-Credits-Charged
Credits charged by this call. Failed and non-chargeable calls return 0 in the header.
billing.creditsRemaining
X-Credits-Remaining
The credit balance after the call.
billing.creditsRefreshAt
X-Credits-Refresh-At
The next monthly credit refresh as an ISO 8601 timestamp. Trial and non-renewing balances return null and omit the header.

All authenticated API-key calls expose the billing headers, including validation errors and zero-credit status or management requests. Only successful chargeable JSON responses add the billing object to the response body.

When credits run out

If your balance is lower than the cost of a request, the API returns HTTP 402 and charges nothing. The error includes the credits needed, your balance and a link to change plan.

{
  "statusCode": 402,
  "statusMessage": "Payment Required",
  "data": {
    "success": false,
    "error": {
      "code": "INSUFFICIENT_CREDITS",
      "message": "This request costs 35 API credits. Upgrade your plan or wait for your monthly refresh: https://propertyinsights.co.uk/billing",
      "required": 35,
      "available": 12,
      "upgradeUrl": "https://propertyinsights.co.uk/billing"
    }
  }
}

Flood risk API parameters

NameRequiredTypeDescription
postcodeNostringFull England or Wales postcode. Alternatively provide coordinates.
latitudeNonumberLatitude when postcode is omitted.
longitudeNonumberLongitude when postcode is omitted.
radiusMetresNointegerNearby flood-defence search radius from 25 to 2,000 metres. Defaults to 250.

Source and coverage

Source
Environment Agency, Natural Resources Wales, SEPA and Ordnance Survey (OS Terrain 50 elevation)
Coverage
England, Wales and Scotland (partial)

This is mapped screening data, not a property-specific flood assessment. An empty result does not establish that a property has never flooded or is insurable.

Example request

curl -X GET "https://propertyinsights.co.uk/api/v1/property/flood-risk?postcode=ZZ1%201ZZ" \
  -H "x-api-key: YOUR_API_KEY"

Example response

{
  "success": true,
  "data": {
    "location": {
      "postcode": "ZZ1 1ZZ",
      "country": "england",
      "latitude": 52.123,
      "longitude": -1.234,
      "radiusMetres": 250
    },
    "coverage": "england",
    "complete": true,
    "riskLevel": "medium",
    "risks": {
      "riverAndSea": {
        "riskLevel": "medium",
        "count": 1,
        "details": [
          {
            "type": "river",
            "classification": "2"
          }
        ]
      },
      "riverAndSeaLikelihood": {
        "riskLevel": "medium",
        "count": 1,
        "details": [
          {
            "classification": "Medium",
            "minimumDepthMetres": 0
          }
        ]
      },
      "surfaceWater": {
        "riskLevel": "none",
        "count": 0,
        "details": []
      },
      "reservoir": {
        "riskLevel": "none",
        "count": 0,
        "details": []
      },
      "coastalErosion": {
        "riskLevel": "none",
        "count": 0,
        "details": []
      },
      "coastalGroundInstability": {
        "riskLevel": "none",
        "count": 0,
        "details": []
      },
      "historicFlooding": {
        "riskLevel": "none",
        "count": 0,
        "details": []
      },
      "floodDefences": {
        "riskLevel": "low",
        "count": 1,
        "details": [
          {
            "name": "Fictional Flood Wall",
            "distanceMetres": 85
          }
        ]
      }
    },
    "elevation": {
      "metres": 12.3,
      "source": "OS Terrain 50",
      "resolutionMetres": 50
    }
  }
}

OpenAPI specification

Authentication, parameters, billing headers and response schemas are also published in the machine-readable OpenAPI documents in JSON and YAML.