West Sussex

Horsham planning data

6,416 planning applications from Horsham, available as JSON over REST or through the MCP server. 10 fields are populated on at least 90% of records.

6,416

Applications

1,059

Enforcement notices

6,842

Appeals

1930–2026

Date range

Field coverage

Measured across all 6,416 records. This is what is actually filled in, not what the council's portal offers — ask get_council_fields for the same numbers from an MCP client.

Reliable — 90% or more of records

Field	Populated	Coverage
`address`	6,416	100.0%
`description`	6,416	100.0%
`reference`	6,416	100.0%
`ward`	6,201	96.6%
`application_type`	5,965	93.0%
`received_date`	5,964	93.0%
`status`	5,960	92.9%
`status_normalized`	5,960	92.9%
`decision_level`	5,955	92.8%
`applicant_name`	5,901	92.0%

Partial — use with care

Field	Populated	Coverage
`decision`	5,665	88.3%
`decision_date`	5,664	88.3%
`decision_normalized`	5,613	87.5%
`postcode`	5,312	82.8%
`case_officer`	4,692	73.1%
`officer_id`	4,692	73.1%
`agent_id`	4,621	72.0%
`agent_name`	4,621	72.0%
`alternative_reference`	4,146	64.6%
`agent_phone`	3,993	62.2%
`agent_email`	3,931	61.3%
`agent_company`	3,634	56.6%
`standard_type`	1,601	25.0%

Rarely or never published

Field	Populated	Coverage
`appeal_decision`	281	4.4%
`appeal_decision_normalized`	281	4.4%
`property_id`	46	0.7%
`development_type`	0	0.0%
`easting`	0	0.0%
`northing`	0	0.0%
`officer_recommendation`	0	0.0%

Query it

curl -H "X-Api-Key: $KEY" \
  "https://ukplanningapi.co.uk/v1/applications?council_id=291&limit=5"

Council id for Horsham is 291. Full endpoint reference →

Get a key for Horsham data

500 requests a month, free. No card, no password.