Skip to content
UK planning applications API

The UK planning applications API

Planning application data and planning conditions as JSON, from one REST API. Search by council, postcode, keyword, status or date and pull results straight into your own tools, with a free demo key to start.

Plans

Priced by records: each application or condition returned counts as one. The same record returned again in the same month does not count twice. API plans are separate from the website plans, and you can cancel any time.

Demo

Free

one-off

100 records, once

  • Application data
  • Agent contact fields
  • Conditions endpoints
API Starter

£49

a month + VAT

2,500 records a month

  • Application data
  • Agent contact fields
  • Conditions endpoints
API Pro
Contacts

£149

a month + VAT

10,000 records a month

  • Application data
  • Agent contact fields
  • Conditions endpoints
National / bulk

From £399

a month + VAT

Higher volumes, agreed with you

  • Application data
  • Agent contact fields
  • Conditions endpoints

Works with Claude and other AI assistants: every plan, including the free demo, connects to our MCP server. Set up your assistant

The Leads website plan includes 1,000 API records a month with agent contact fields and conditions. Allowances add up if you also buy an API plan.

Every key and plan is covered by the API & Data Licence (version 2026-10-24): use the data in your own organisation and show individual records to your own users, but don't resell it, redistribute it in bulk or use it to train or build a competing dataset.

Your API key

Create a free account and get a demo key straight away: 100 records to try the API, no card needed.

Your first request

Send your key as a bearer token, from your server. JSON comes back, with your remaining records in the response headers. 60 requests a minute per key.

curl "https://planningsignal.co.uk/api/v1/applications?authority=Camden&since=2026-09-01&limit=5" \
  -H "Authorization: Bearer ps_live_your_key_here"

Quick start in curl, JavaScript and Python

Documentation

Planning application data, ready to build on

Every council publishes its planning applications in its own way. The planning data API gives you one consistent shape for all of them, so you write your integration once and it works for every council in the country.

Feed your CRM or lead pipeline

Pull new applications by council, postcode radius or keyword into the tools your sales team already uses, the day they are published.

Power a property or proptech product

Show planning history and live applications on listings, valuations, surveys and site-finding tools, with individual records shown to your own users.

Monitor sites and clients

Check a list of addresses or areas on a schedule and alert your team when something is filed, decided or appealed.

Research and reporting

Count applications, approvals and decision times by council and period for market studies, board packs and local plan evidence.

Track conditions

On API Pro, search the conditions attached to approvals by discipline and phrase, and route the ones your specialists can discharge.

Build with AI tools

Use the MCP server to give Claude, Cursor and other MCP clients live planning data as tools, with the same key and the same allowance. Set up your AI assistant.

What a planning permission API call returns

Each record carries the fields you need to put planning data to work: the council and its reference, the site address and postcode, a description of the proposal, the application type, its start date, the current status and the decision. Where an application has a site location, the response includes it, so you can map records or search by radius.

API Pro adds the agent contact fields on each record, for teams who need to reach the firm behind a scheme, and the conditions endpoints. Responses are paged, filters combine, and every response tells you how many records you have left this month.

Start with the quick start, check the fields reference, then choose the plan that fits your volume. Watching your own list of sites instead? Portfolio Monitor does it with no code.

Planning data API questions

What is the Planning Signal API?

A read-only REST API for UK planning application data. You send a request with your key and get JSON back: applications with their reference, council, address, description, dates, status and decision, plus the conditions attached to approvals.

How do I get UK planning application data into my own system?

Create a free account, copy your demo key and call the applications endpoint. The demo gives you 100 records once, with no card needed. When you are ready for more, API Starter is £49 a month + VAT for 2,500 records a month.

How is the planning data API priced?

By records. Each application or condition returned counts as one, and the same record returned again in the same month does not count twice. API Starter is £49 a month + VAT, API Pro is £149 a month + VAT, and higher volumes start from £399 a month + VAT.

Can I get planning conditions from the API?

Yes, on API Pro and above. The conditions endpoints return the conditions attached to an approval, and you can search them by discipline and by phrase, so you can build a feed of the conditions your clients need to discharge.

Which filters can I use?

Council, postcode with a radius, keyword and date ranges, with paging for large result sets. The fields reference lists every field, its type and when it is empty.

Is there an OpenAPI spec, and can I use the API from Claude?

Yes to both. The OpenAPI 3.1 spec is published for client generation, and the MCP server lets Claude Code, Claude Desktop, Cursor and other MCP clients use the API as tools. The AI assistants page has the setup.

Can I resell the data?

You can use it inside your organisation and show individual records to your own users. Resale, bulk redistribution and building a competing dataset are not allowed. The API & Data Licence has the full terms.

Licence and attribution

Using the API or the MCP server means accepting the API & Data Licence. In short:

  • Use the data inside your organisation, and show individual records to your own users. Bulk redistribution, resale, and building or training a competing planning dataset or model are not allowed.
  • Where you show the data publicly, credit Planning data from Planning Signal, and keep any attribution a record carries.
  • Agent contact fields are business contact details but can identify people. You are responsible for using them lawfully under UK GDPR and PECR, including not sending unsolicited marketing emails to individuals without consent.
  • Council registers can be incomplete or late, and nothing here is legal or planning advice.
  • Delete stored data within 30 days of your plan ending.

Questions, or need more than Pro? Contact us. Step-by-step account help is in the help centre.