Hampshire

Portsmouth planning data

4,365 planning applications from Portsmouth, available as JSON over REST or through the MCP server. 12 fields are populated on at least 90% of records.

4,365

Applications

—

Enforcement notices

4,765

Appeals

1969–2026

Date range

Field coverage

Measured across all 4,365 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`	4,365	100.0%
`description`	4,365	100.0%
`received_date`	4,365	100.0%
`reference`	4,365	100.0%
`ward`	4,357	99.8%
`application_type`	4,343	99.5%
`applicant_name`	4,209	96.4%
`decision_level`	4,200	96.2%
`postcode`	4,015	92.0%
`alternative_reference`	3,985	91.3%
`decision`	3,931	90.1%
`decision_date`	3,927	90.0%

Partial — use with care

Field	Populated	Coverage
`decision_normalized`	3,913	89.6%
`agent_id`	3,719	85.2%
`agent_name`	3,719	85.2%
`agent_email`	3,712	85.0%
`agent_company`	3,454	79.1%
`agent_phone`	3,412	78.2%
`case_officer`	3,371	77.2%
`officer_id`	3,371	77.2%
`standard_type`	1,461	33.5%
`status`	1,034	23.7%
`status_normalized`	1,034	23.7%

Rarely or never published

Field	Populated	Coverage
`appeal_decision`	60	1.4%
`appeal_decision_normalized`	60	1.4%
`property_id`	19	0.4%
`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=375&limit=5"

Council id for Portsmouth is 375. Full endpoint reference →

Get a key for Portsmouth data

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