Draft the application
from your own system
Create draft planning applications in Planda Portal directly from your CRM or platform. No re-entering data.
What our API does
Your team already has most of the information needed for a planning application. Instead of entering it again into a submission portal, our Partner API creates a draft application automatically from your existing system.
Your team simply reviews the draft, fills any gaps, runs validation, pays and submits through Planda Portal as usual.

Why agents use it
Drafting time falls on average by 70%
Turn a 15-minute application into five. Around 95% of every form is pre-filled, with an end-to-end digital workflow and bespoke steps where your process differs.

Fewer mistakes, without giving up control
The API removes manual copying, while AVA checks every application against government requirements. Your team still reviews, pays for and submits every application—nothing reaches a council automatically.

Free, and quick to get hold of.
There's no cost to access the API. An organisation owner or admin generates the API key themselves from within the Portal. There's no separate integration fee.

One build, every council.
Integrate once with Planda Portal to reach every supported local planning authority. Query the API to pull live status updates on your applications, so your records stay current without manual checking.

What we need from you
No external tools, developer accounts, or middleware required.
A Planda Portal organisation.
If you are not on Planda Portal yet, join now. It takes 2 minutes.
An Owner/Admin to generate the key.
An owner or admin must generate the key. We recommend using an account belonging to someone permanent in your organisation, as the key will stop working if that person leaves.
Somewhere secure to hold it.
Treat the key as a production secret. Never in email, chat, logs or browser code. Keys expire after a year and can be regenerated in the platform.
The ability to make server-side HTTPS calls.
Any modern language will do, and if your CRM supports outbound webhooks or custom API actions, that should be enough.
Site location data on every application.
Every application needs site location data (address, UPRN, coordinates, boundary or location plan), so we can identify the correct planning authority.
A named technical contact.
One person on your side who owns the build.
Not technical?
Suggested FAQ block
Can the API submit applications to the council?
No. It creates and updates drafts and handles documents. Review, payment and submission stay with your team in the Portal. That is deliberate: nothing goes to a council without a person deciding it should.
Do applications created by the API look any different?
No. They are ordinary Planda Portal applications owned by your organisation, visible in the Portal immediately.
Can we test before we commit?
Yes. Ask for a test organisation and run the flow end to end before you build anything.
What's the cost to access the API feature?
Zero.
Can we turn it off?
Yes. You can revoke the key from your account page at any point.


