Location intelligence

Property Due Diligence API

Generate prioritised enquiry prompts from open screening data with optional OS NGD property context.

Endpoint

GET/api/v1/property/due-diligence

Provide a postcode, or both latitude and longitude. Add a UPRN only when OS NGD property context is required.

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

Planning, full English flood, ground, environmental and optional OS NGD evidence can be combined.

Wales

Partial

Welsh flood and Great Britain ground/OS evidence are available. Planning Data, English noise and source-protection layers are not.

Scotland

Partial

Great Britain ground and optional OS context plus UK-AIR can be returned. Planning and flood evidence are not configured.

Northern Ireland

Not supported

The configured planning, flood, ground and OS NGD evidence does not provide a meaningful combined screen.

Cost per successful request

Pricing

The composite request costs 18–30 credits based on selected environmental factors. Supplying a UPRN adds 35 credits for OS property context.

API credits: 18–30 credits; add 35 with UPRN
Rejected or failed: No charge

What the API provides

Prioritised findings

Converts matched evidence into high, review or awareness enquiries with a plain reason and recommended action.

Concise check summaries

Returns small planning, flood, environmental and ground summaries instead of embedding every underlying API response.

Normalised environmental factors

The environmental section contains the requested factor statuses and reuses the already fetched flood and ground evidence without making duplicate provider calls.

Optional OS property context

With uprn, adds a short building summary covering use, form, floors, age, construction, roof and land use where available.

Response guide

Field	Meaning
data.property	Resolved location, radius and optional UPRN.
data.complete	False when an expected check is partial, unavailable or outside coverage.
data.riskLevel	Overall none, medium or high triage level.
data.enquiries[]	Prioritised code, category, title, reason and recommended action. Raw evidence is omitted.
data.checks	Concise planning, flood, environmental and ground status summaries.
data.building	Optional concise OS building summary. Null unless a UPRN is supplied and matched.

Useful request variants

Add OS NGD property context

curl -X GET "https://propertyinsights.co.uk/api/v1/property/due-diligence?postcode=ZZ1%201ZZ&uprn=100023456789&radiusMetres=250" \
  -H "x-api-key: YOUR_API_KEY"

Increase the screening radius

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

Not included

No official local search, CON29, CON29DW, environmental report, flood report or CON29M is ordered.
An official address-level radon report, authorised landfill, BGS GeoSure, contaminated land and groundwater susceptibility are not included. Their gaps are explicit rather than returned as no risk.
Highways adoption, public rights of way, utility apparatus, planning enforcement and building control are not included.

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 header	Meaning
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.

Parameters

Name	Required	Type	Description
postcode	No	string	Full Great Britain postcode. Alternatively provide coordinates.
latitude	No	number	Latitude when postcode is omitted.
longitude	No	number	Longitude when postcode is omitted.
radiusMetres	No	integer	Planning and recorded-landslide screening radius from 25 to 2,000 metres. Defaults to 250.
factors	No	string	Comma-separated environmental factor names or all. Defaults to all.
uprn	No	string	Optional UPRN used to add OS NGD building and land-use context.

Source and coverage

Source: Planning Data, Environment Agency, Natural Resources Wales, Mining Remediation Authority, British Geological Survey, and optional Ordnance Survey NGD
Coverage: Planning and flood data for England and Wales; ground data for Great Britain where records are available

This endpoint is an early-warning screen. It does not replace official conveyancing searches, title review, local authority replies, drainage enquiries or professional advice.

Example request

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

Example response

{
  "success": true,
  "data": {
    "property": {
      "postcode": "ZZ1 1ZZ",
      "country": "england",
      "latitude": 52.123,
      "longitude": -1.234,
      "radiusMetres": 250
    },
    "complete": true,
    "riskLevel": "high",
    "enquiryRecommended": true,
    "enquiryCount": 1,
    "enquiries": [
      {
        "code": "FLOOD_RIVERS_OR_SEA",
        "category": "flood",
        "priority": "high",
        "title": "River or sea flood mapping",
        "reason": "The location matches published flood mapping.",
        "action": "Obtain an official flood search and ask about historic flooding and insurance."
      }
    ],
    "checks": {
      "planning": {
        "status": "complete",
        "constraintCount": 0
      },
      "flood": {
        "status": "complete",
        "riskLevel": "high",
        "matchedRisks": [
          "riversAndSea"
        ]
      },
      "environment": {
        "status": "complete",
        "riskLevel": "high",
        "requestedFactors": [
          "flood"
        ]
      },
      "ground": {
        "status": "complete",
        "riskLevel": "none",
        "coalMining": false,
        "landslideCount": 0
      }
    },
    "building": null
  }
}

OpenAPI specification

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