Help with the UK Planning API, its REST endpoints and its MCP server for ChatGPT, Claude and other AI assistants.
Email help@ukplanningapi.co.uk. We aim to reply within one working day. Please include:
Do not send your API key. We never need it, and we cannot recover one (we store only a hash).
The step-by-step instructions for ChatGPT, Claude, Claude Code and other clients are on the connection page, including what to do if the sign-in does not complete. Sign-in is by an emailed link, so there is no password to reset. If the link does not arrive, check your spam folder, then email us.
Each tool call counts as one request against your monthly allowance, which is shared with the REST API. Your usage is shown on your dashboard.
If a record looks wrong or incomplete, please open an issue on our public tracker: github.com/JanHendrikVermeer/ukplanningapi/issues. Name the council and the application reference so we can find the record and compare it with the council's own register. For example:
Council: Camden Application reference: 2024/1234/P (an example format, not a real record) Tool or endpoint: get_application What came back: decision date empty What the council's register shows: decision date present Date and time of the call: ...
The tracker is public, so leave out your API key and any personal details. If the issue needs either, email us instead.
The records are public planning registers published by councils and the Planning Inspectorate, and we show them as published. Coverage differs by council and by field; the council coverage page shows what each council provides. An empty field does not mean that no such record exists. Where the council's own register is wrong, the council has to correct it at source. Corrections are normally picked up when we next refresh that council's records, but we cannot guarantee when that will be.
Please report it privately, not on the public tracker. Email help@ukplanningapi.co.uk with the subject Security vulnerability. Please include:
Please do not read, change or keep other people's data while testing, and
give us a reasonable time to fix the problem before you publish details.
We aim to confirm receipt within one working day. A machine-readable copy of
this contact is at
/.well-known/security.txt.
If you are named in a planning record and want to ask about it, or you want a copy of the data we hold about your account, see the privacy policy and email us.