UK Planning Applications — by Postcode or Keyword avatar

UK Planning Applications — by Postcode or Keyword

Pricing

from $2.00 / 1,000 results

Go to Apify Store
UK Planning Applications — by Postcode or Keyword

UK Planning Applications — by Postcode or Keyword

Real, live UK planning application data by postcode+radius, free-text keyword, council/authority name, or date range — sourced from PlanIt (planit.org.uk), a free, public aggregator of UK local-authority planning application registers.

Pricing

from $2.00 / 1,000 results

Rating

0.0

(0)

Developer

dan boulton

dan boulton

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 days ago

Last modified

Categories

Share

Real, live UK planning application data — search by postcode + radius, free-text keyword, council/authority name, or a received-date range. Sourced from PlanIt, a real, free, public aggregator of local-authority planning application registers across the UK. No scraping of council portals directly — every field is a real PlanIt API response field, passed through un-invented.

Input

FieldTypeNotes
postcodestringe.g. "M16 9HF". Used with radiusKm.
radiusKmnumberDefault 5.
keywordstringFree-text search against the application description.
authoritystringRestrict to one council, e.g. "Manchester".
startDate / endDatestringYYYY-MM-DD, application-received date range.
maxResultsintegerDefault 100, hard cap 5000 (PlanIt's own absolute per-request limit).

At least one of postcode, keyword, or authority is required — this actor refuses an unscoped "everything" query rather than guess one (a real unscoped keyword-only search against PlanIt's full national dataset timed out during testing; scoping by authority or postcode keeps a real query fast and is a genuine, disclosed usage note, not just an input-validation nicety).

Output (one dataset item per application)

{
"reference": "Manchester/115763/FU/2017",
"authority": "Manchester",
"address": "All Bar One 73 - 79 King Street Manchester M2 4NG",
"postcode": "M2 4NG",
"description": "Change of use of pavement for use as an external seating area",
"status": "Permitted",
"decision": "Approved",
"application_type": "Amendment",
"received_date": "2017-05-19",
"decided_date": "2017-07-14",
"last_changed": "2026-09-05T11:18:35.383358",
"planit_url": "https://www.planit.org.uk/planapplic/Manchester/115763/FU/2017/",
"source_url": "https://arcusbe.manchester.gov.uk/pr/s/detail/a1DSl000007GC6AMAW",
"location": {"lat": 53.480914, "lng": -2.242698}
}

Pricing

Pay-per-event: one charge per real application actually returned — never charged for a search that returns nothing. See .actor/pay_per_event_schema.json for the proposed event/price; verify and finalise the real price in the Apify Console's own Monetization tab before publishing (disclosed honestly, same as the Companies House actor's README: the exact checked-in schema format could not be confirmed from a literal authoritative example during a live web search while building this — the code-side Actor.charge() call is real and correct regardless of how the price itself ends up configured).

Rate limits

PlanIt is real and genuinely rate-limited (a live 429 was hit while building/testing this actor). One real retry after a 5s pause is built in; a persistent 429 surfaces as a real, disclosed error rather than being silently retried forever.