West Sussex

Mid Sussex planning data

8,006 planning applications from Mid Sussex, available as JSON over REST or through the MCP server. 17 fields are populated on at least 90% of records.

8,006

Applications

Enforcement notices

6,250

Appeals

1984–2026

Date range

Field coverage

Measured across all 8,006 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`	8,006	100.0%
`description`	8,006	100.0%
`received_date`	8,006	100.0%
`reference`	8,006	100.0%
`application_type`	7,990	99.8%
`status`	7,983	99.7%
`applicant_name`	7,972	99.6%
`status_normalized`	7,963	99.5%
`ward`	7,959	99.4%
`agent_email`	7,939	99.2%
`case_officer`	7,941	99.2%
`officer_id`	7,941	99.2%
`alternative_reference`	7,699	96.2%
`decision_level`	7,655	95.6%
`decision`	7,425	92.7%
`decision_date`	7,421	92.7%
`decision_normalized`	7,413	92.6%

Partial — use with care

Field	Populated	Coverage
`postcode`	7,105	88.7%
`agent_phone`	6,786	84.8%
`agent_id`	6,222	77.7%
`agent_name`	6,222	77.7%
`appeal_decision`	5,503	68.7%
`standard_type`	5,458	68.2%
`agent_company`	4,486	56.0%

Rarely or never published

Field	Populated	Coverage
`appeal_decision_normalized`	158	2.0%
`development_type`	0	0.0%
`easting`	0	0.0%
`northing`	0	0.0%
`officer_recommendation`	0	0.0%
`property_id`	0	0.0%

Query it

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

Council id for Mid Sussex is 329. Full endpoint reference →

Get a key for Mid Sussex data

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