API Documentation

Search and filter planning applications with full-text search, postcode filtering, and faceted results. Free and Alerts Pro API keys search a patch — a council (up to 5), postcode districts (up to 10), or a point with a radius up to 25 km — and see applications 7 days after PlanNexus first records them (meta.notice and the X-PlanNexus-Data-Delay header say so). Live, nationwide data is Starter, or the 14-day Starter trial.

Find planning applications near a geographic point.

Get full details for a single planning application — including planning constraints at the site and, where the property has one, its Energy Performance Certificate (rating band and technical facts, matched by UPRN, served under OGL with attribution; property owners can ask us to suppress their EPC — see the privacy policy). Discharge-of-conditions and variation-of-condition applications also carry parent_reference and parent_application_id — the permission they act on, resolved within the authority where we hold it.

List documents associated with an application.

Get the status change history for an application.

Planning constraints at a point — conservation areas, listed buildings, flood zones, green belt, tree preservation orders and more, from national open datasets. Query by coordinates or postcode.

Paid. Stream a filtered result set as a CSV download — up to 25,000 rows per call, metered per-row against your monthly export allowance. Takes the same filters as /v1/applications, plus:

Paid. The most-active planning agents within a filtered result set, as CSV — same filters as /v1/applications.

List all local authorities in the database.

Public — no auth. League table — approval rate, decision speed and volume for every authority (rolling 12 months, official MHCLG PS2). Rendered at plannexus.io/leagues/planning.

Paid. One council's scorecard vs national + regional averages, with rank and the major/minor/other split.

Paid. Full quarterly approval/timeliness series, 1979 to present.

Public — no auth. Headline approval rate, national average and rank for one council.

Public — no auth. One council's rolling-year approval rate, refusal rate and share decided on time against the national figure, the major / minor / householder split, and a calendar-year history (partial years marked). Rendered at plannexus.io/leagues/planning/{gss} for every authority with returns in the latest four quarters (310 at the time of writing; the history goes back to 1979).

Paid. Busiest authorities by applications received (live; 12-month and last-90-day volumes).

Paid. One authority's volume, application-type mix and 24-month trend.

Public — no auth. The development-pressure map in five quantile bands of applications received per cell — the band only, nothing else per cell. Rendered on plannexus.io/leagues/planning/{gss}; the counts, approval record, brownfield sites and hotspots are on the paid endpoint below.

Paid. MEES map: every rated EPC certificate placed on the council's hex grid through its UPRN (98.7% carry one), with all-stock and private-rented counts per cell and the private-rented below-C and F/G shares where a cell has at least 30 rated private-rented certificates; ranked hotspots. Rebuilt quarterly.

Paid. Development pressure: a metre-true hex grid over the council (500 m borough / 1 km district / 2 km county) with applications received in the last 12 months, determinations and approvals in the last 24 (a cell carries its own approval rate past 10 determinations) and brownfield-register sites per cell — as a GeoJSON FeatureCollection plus ranked hotspots and the share of activity in the busiest tenth of cells. Tracked councils only; cached six hours.

Paid. Most-active planning agents by application volume (national, or scoped to one authority).

Paid. Property-market summary for one council from HM Land Registry Price Paid — median price, sales volume and year-on-year change (England & Wales; YoY suppressed on thin samples).

Public — no auth. Headline median price and sales volume for one council.

Public — no auth. Energy-efficiency league built from 22M+ domestic EPC certificates — share rated C or better and mean SAP score per council (suppressed under 100 certificates). Rendered at plannexus.io/leagues/energy.

Paid. One council's EPC profile: rating distribution, mean SAP score, retrofit signals, and the MEES figures — certificates rated F or G (cannot be let without an exemption) and below C (the proposed rental standard), with the national comparison, for all stock and — under private_rented — for the private-rented stock MEES applies to (tenure as recorded on the certificate; tenure_known_share says how complete it is).

Public — no auth. Headline share rated C+ and rank for one council.

Public — no auth. Appeals league from Planning Inspectorate casework — overturn rate per council (appeals allowed / decided; suppressed under 20 decided). Rendered at plannexus.io/leagues/appeals.

Paid. Agent win rates at appeal — who actually gets refusals overturned.

Paid. One council's appeal record: overturn rate vs the national average, volume and 10-year trend.

Public — no auth. Headline overturn rate and rank for one council.

Any signed-in caller. One council, optionally one application type. A type too thin to answer on widens to the whole council and says so in basis.widened_from.

Any signed-in caller. The whole council in one call: `all` plus every application type with its own sample, largest first. Thin types come back as insufficient with their count — never silently widened.

Any signed-in caller. The same comparison keyed off a live application — its council and type — so a record in a feed or alert carries its odds and timescale.

Paid. PropertyDossier — one call, everything we hold about a site: planning history and outcomes, live constraints, flood zone, LPA performance, appeals record, heritage, market context, EPC (where present), and area ownership statistics. Every layer carries its own provenance (source + retrieved_at) and degrades honestly — a layer we can't serve says so and why, and the dossier states its own outcome-coverage grade for the area. Locate by postcode, coordinates, UPRN or address. Metered per tier: Free/Alerts Pro 25, Starter 250, Pro 1,500 lookups/mo; Enterprise unlimited. See a real response at plannexus.io/samples/dossier.

Create a webhook subscription to receive notifications for new applications or status changes. Data Feed plan.

List your webhook subscriptions.

Corporate and overseas-held Land Registry titles (CCOD/OCOD) by postcode or district. Company ownership only. Paid plans.

S106 covenants and CIL liabilities attached to a consent, by reference or authority. Coverage is the Exacom councils and is stated per response. Paid plans.

Council enforcement registers — alleged breaches under investigation: the council's reference, site address and postcode, what is alleged, status, date opened and the date a formal notice was served. Newest first, up to 200. Every response states its coverage: about half of idox councils publish no register, so absence is never evidence of no enforcement. Any signed-in caller. Per-council picture: /v1/analytics/enforcement/{gss} (paid) and the scorecard's Enforcement section.

Individual sales from HM Land Registry Price Paid — the comparables. Every recorded sale at a postcode or across an outward code: price, date, address, property type, tenure, new-build flag, category; newest first, up to 200. Any signed-in caller. Council-level median and trend: /v1/analytics/market/{gss}.

The registered land parcel under a point and the parcels touching it (within 0.5 m), as GeoJSON with INSPIRE ids and areas — HM Land Registry INSPIRE Index Polygons, attribution carried on the response. No owner names (not in the open polygons; corporate owners are on /v1/ownership). Any signed-in caller.

The latest Energy Performance Certificate at a UPRN: band, score, potential, floor area, dates, tenure as recorded, and what the band means under MEES for a let property (mees_status). Property-level only — address fields are never served and erasure suppressions are honoured. Any signed-in caller.

Sites on councils' brownfield land registers: dwelling estimates, permission status, deliverability, last update. Open data; any signed-in caller.

One UPRN: the OS Open UPRN point, its ONS postcode, any council-published address, and the applications we hold at it. Any signed-in caller.

Addresses with UPRNs for one postcode from the council gazetteers we hold (not a national address product). Paid plans.

Adjoining properties for a point.

The same lookup keyed by one of our applications (its geocoded site). 404 when the application has no location.

Merge-ready rows, one per property: recipient, salutation, address split into lines, and the planning facts. Filter by council or a radius. Paid plans; metered as export rows.

Applications in scope minus those already written to, dismissed, or on your do-not-write list — with counts saying why each excluded row is excluded. Scope by saved_search_id, authority_gss, or lat + lng + radius.

Freeze a recipient list from the worklist plus what to say: filters, optional application_ids, template_id or body text, letterhead_id, provider_id, test_mode. Creates a draft; nothing is sent or metered yet.

Push the campaign into your print account. Metered once here as export rows (429 if it would exceed your ceiling, and nothing is sent). Runs in the background; poll the campaign and its /letters for provider ids, statuses and any provider error text.

Connect your own print account (provider: stannp | docmail | intelliprint | postgrid | clicksend, with that provider's credential fields). Verified against the provider before it is stored, encrypted. GET /v1/letters/providers/available lists what can be connected and which fields each needs.

The first letter rendered exactly as it will be sent, with the address-window outline. POST /v1/letters/preview.pdf renders any text with sample data.

Never write to this address again ({ address_line_1, postcode, reason }). Matched on the normalised first line + postcode so a re-filed application at the same property is caught. POST /v1/letters/{letter_id}/suppress does it straight from a sent letter.

'Not writing to these' — drop application_ids from the worklist without a letter.

The {{fields}} a letter body, heading or signature may use: salutation, recipient_name, address lines, council, application_reference, application_type, date_received, description, portal_link, today.