Skip to main content

Planning applications

Returns planning intelligence for UK properties: nearby planning applications, conservation area and listed building (heritage) status, and Article 4 direction checks. Application data is sourced from PlanIt (England, Wales, Northern Ireland) and the Scotland Spatial Hub (Scottish postcodes — routing is automatic), with heritage and Article 4 data from the national Planning Data API. Results are queried live against the upstream sources; geometry, paginated, and conservation boundary responses are cached for up to 4 hours. Required scope: planning:read Cost: 1 request per call Available on: Starter, Professional, Business

Search planning applications by postcode

Search nearby planning applications for any UK postcode — no property ID needed. The postcode is geocoded, then applications within the radius are returned with summary statistics.

Request

Response

status is normalised to pending / approved / refused / withdrawn / other, and source is planit or scotland_spatial_hub. If planning data is temporarily unavailable the endpoint still returns 200 with an empty applications list and error_message set.

Get planning applications for a property

Nearby planning applications for a property already in the platform, using its stored coordinates. Same response item shape and summary as the postcode search.

Request

Response

Get heritage status for a property

Checks whether a property sits in a conservation area or is a listed building, with a combined restriction summary.

Request

Response

restrictions.level is none, medium (conservation area), or high (listed building). restrictions.has_article4 is always false here — use the dedicated Article 4 endpoint below.

Get Article 4 direction status

Checks whether an Article 4 direction (removal of permitted development rights — commonly used to restrict HMO conversions) applies at the property’s postcode.

Request

Response

Get nearby applications (Planning Data API)

A postcode-based application lookup against the national Planning Data API. For most use cases prefer /{property_id}/applications above, which uses coordinates and covers Scotland.

Request

Response

Get applications by geometry

Coordinate-based application search (more precise than postcode matching), with optional GeoJSON output for mapping. Cached for 4 hours.

Request

Response

Get all applications (paginated)

Retrieves a larger result set via multiple upstream paginated requests — useful for dense urban areas with more than 100 applications. Cached for 4 hours.

Request

Response

Get conservation area boundaries (GeoJSON)

Conservation area boundaries around the property as a GeoJSON FeatureCollection with MULTIPOLYGON geometry — ready for map overlays. Cached for 4 hours.

Request

Response

Use cases

  • HMO due diligence — Check Article 4 directions before underwriting an HMO conversion
  • Refurbishment risk — Conservation area or listed status changes what works need permission
  • Development signals — Nearby pending applications indicate area investment momentum
  • Map overlays — GeoJSON boundaries and application points for portfolio mapping tools
  • Flood risk — Flood zone overlap by point or property
  • Heritage status — Listed building & conservation area data by property or outcode
  • Properties — Look up property UUIDs to feed into these endpoints