Location intelligence

Broadband Availability API

Retrieve postcode-level Ofcom broadband availability, predicted speeds, and address coverage percentages without exposing individual addresses or UPRNs.

Endpoint

GET/api/v1/connectivity/broadband

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	Yes	string	Full UK postcode.

Source and coverage

Source: Ofcom
Coverage: UK postcodes where Ofcom coverage records are available

Example request

curl "https://propertyinsights.co.uk/api/v1/connectivity/broadband?postcode=SW1A%201AA" \
  -H "x-api-key: YOUR_API_KEY"

Example response

{
  "success": true,
  "data": {
    "postcode": "SW1A 1AA",
    "addressCount": 2,
    "broadband": {
      "maxDownloadMbps": 17,
      "maxUploadMbps": 1,
      "basic": {
        "available": true,
        "addressCoveragePercent": 100
      }
    }
  }
}

OpenAPI specification

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