Property planning history
GET /v1/property/{uprn}/planning-historyPlanning history AT this property: applications linked to the unit or its building — each with decision, dates, appeal, CIL liability, development type and `match_level` (`unit`, `building`, or `nearby` within 25 m when nothing is linked) — a summary (approved / refused / withdrawn / pending), what needs consent here from the designation flags read three-valued (`applies` against `unchecked`), the LPA, and `coverage`: official planning data covers the 33 London boroughs today, so `status: not_covered` outside London is a different answer from `no_applications`, and is not charged. UK only.
Same call over MCP
Planning history at a propertyproperty_planning_historyAuthenticate with an API key from the API & MCP Hub. The same call is available as an MCP tool at the same price.
Inputs
Before you call it
- uprn
- A UPRN is the Unique Property Reference Number every UK address carries. Narrow the address with address_autocomplete, which is free, then address_resolve returns the UPRN for 8 credits. property_summary and address_by_postcode return UPRNs too.
Request
Calling GET /v1/property/{uprn}/planning-history
curl "https://api.marketcode.ai/v1/property/200003448393/planning-history" \
-H "Authorization: Bearer $MARKETCODE_API_KEY"Send your API key as a Bearer token. Every response carries credits_charged and credits_remaining.
Inputs
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| uprn | Path | integer | Yes |
Price and licence
What it costs, and where the data comes from
Property planning history costs 1 credit per successful call over MCP and over REST, and the two surfaces share one credit balance.
The price covers licensed records in the response. A call that fails is not charged.
Credits are granted on sign-up and bought in packs; the pricing page lists every call.
Related
Endpoints used with Property planning history
- Chosen planning designation checksFree
planning_checkThe planning designation checks you choose, for one location, in one call. `checks` is any of: article_4, brownfield, ancient_woodland, heritage_at_risk, tpo, aqma, scheduled_monument, sssi, agricultural_land, flood_risk, green_belt, listed_buildings, aonb, national_park, conservation_area — omit it for all fifteen. Each check reports its own result, and one that could not be read says `status: unknown` rather than disappearing. Use `planning_designations` for the fixed bundle of thirteen; use this when you need SSSI or agricultural land grade, or only two or three checks. Give either `postcode` or `location` as "lat,lng". UK only.Same category - Approval rate and decision time nearby2 credits
planning_precedentsWhat happened to applications like this one nearby — the planning precedent record. Give a point (`lat`/`lon`) or an `lpa_code`, optionally narrowed by `application_types` (substrings of the authority's own type labels, e.g. ["Householder"]).Same category - Planning histories for up to 100 properties1 credit
property_planning_history_batch`property_planning_history` for up to 100 properties in one call, per-item outcomes (ok | no_applications | not_covered | not_found | error) in input order. Charged per property answered — the sum of the single calls, never more; not_covered rows are free. UK only.Same category - Planning designations at a locationFree
planning_designationsEvery planning designation affecting a location, in one call: conservationSame category - Planning authority for a locationFree
planning_applicationsThe local planning authority for a location and its planning-portal URL.Same category
FAQ
Questions about Property planning history
How much does `property_planning_history` cost?
+
Property planning history costs 1 credit per successful call over MCP and over REST, and the two surfaces share one credit balance. The price covers licensed records in the response. A call that fails is not charged.
Do I need to resolve the address first?
+
Yes. property_planning_history takes a UPRN, not an address. Start with address_autocomplete (free) to narrow the address, then address_resolve (8 credits) to get the UPRN. An assistant with the MarketCode skills installed does both steps on its own.
How do I authenticate?
+
Send your API key as a Bearer token in the Authorization header. Keys are created in the API & MCP Hub, shown once and revocable. Every response carries the credits charged and your remaining balance.
Is there an MCP version?
+
Yes. The property_planning_history tool on the MarketCode MCP server is the same call at the same price, signed in with OAuth rather than a key, so Claude, ChatGPT, Codex and Cursor can run it in a conversation.
Where does the data come from?
+
The answer is computed by MarketCode. Coverage is the UK.
Can I store or republish the results?
+
The response includes records we license. Use them in your own analysis, reports and products; bulk redistribution of the raw records or building a competing dataset from them is not covered. Ask us if you need a redistribution licence.
Does `property_planning_history` change anything?
+
No. The tool is annotated read-only on the server, so it never writes to your data or ours and an assistant can call it without a confirmation step.
Try Property planning history on a real address.
30-minute call. We'll provision a key and walk through the endpoint on your use case.