London Planning Applications Scraper

Extract London Planning Applications planning applications for construction project research, permit monitoring and development analysis. London Planning Applications Scraper collects public information into one complete dataset table, ready to export as Excel, CSV or JSON.

Use search filters or planning application ids, set how many results you need and start the Actor. Search finds matching records; Details retrieves the available information for records you already know.

At a glance	Details
📥 Input	Search filters or planning application ids
📋 Collection modes	Search planning application records; Get planning application details
📤 Output	One row per record, or a failed row for an unsuccessful input
📄 Pagination	Automatic, up to maxResults while more records are available
🔐 Website login	Not required
💾 Export	One dataset view with all fields; Excel, CSV and JSON

What the London Planning Applications scraper collects 📋

Mode	What you receive
Search planning application records	Matching planning applications and the fields published in the search results.
Get planning application details	Available public information for each supplied record. The full output example below shows its actual fields.

The field table and complete examples below show the information this Actor returns. Optional values depend on what the source publishes for the selected record.

Coverage for this Actor:

• Covers planning applications available in the London Planning Datahub. Council coverage and record completeness vary.

How to scrape London Planning Applications 🚀

1. Choose Search planning application records or Get planning application details.
2. Complete the search filters or planning application ids.
3. Set Maximum results. The minimum is 1.
4. Start the Actor and review the saved dataset.
5. Export the results or connect them to your workflow.

Search planning application records — input example

{
  "mode": "search",
  "maxResults": 10
}

Get planning application details — input example

{
  "mode": "details",
  "recordIds": [
    "Islington-P2025_0271_FUL"
  ],
  "maxResults": 1
}

maxResults limits all saved rows for each search or supplied record, including a failed row. It does not guarantee that the source has that many matching records. A detail lookup normally returns one record, although sources with multiple revisions or establishments can return more.

London Planning Applications data fields and complete output 📦

Each result stays in one row. Every returned field appears in the same dataset view, including list fields and additional published facts. Fields unavailable for a particular record remain empty.

Field	Included data
result_type	Selected collection mode.
input	Submitted search settings, record link or record number.
status	Success or failed outcome.
error_code	Failure category for an unsuccessful input.
error_message	Readable explanation for an unsuccessful input.
decision_conditions	Decision conditions, when published.
actual_commencement_date	Actual commencement date, when published.
decision_target_date	Decision target date, when published.
lpa_name	Lpa name, when published.
centroid_northing	Centroid northing, when published.
last_updated	Last updated, when published.
development_type	Development type, when published.
ward	Ward, when published.
parking_details	Parking details, when published.
uprn	Uprn, when published.
last_date_consultation_comments	Last date consultation comments, when published.
decision	Decision, when published.
bo_system	Bo system, when published.
postcode	Postcode, when published.
secondary_street_name	Secondary street name, when published.
last_synced	Last synced, when published.
appeal_decision_date	Appeal decision date, when published.
application_type	Application type, when published.
decision_date	Decision date, when published.
borough	Borough, when published.
wgs84_polygon.type	Wgs84 polygon / type, when published.
wgs84_polygon.coordinates	Wgs84 polygon / coordinates, when published.
lpa_app_no	Lpa app no, when published.
valid_date	Valid date, when published.
description	Description, when published.
centroid_easting	Centroid easting, when published.
site_number	Site number, when published.
lapsed_date	Lapsed date, when published.
date_building_work_started_under_previous_permission	Date building work started under previous permission, when published.
title_number	Title number, when published.
decision_process	Decision process, when published.
epc_number	Epc number, when published.
street_name	Street name, when published.
appeal_start_date	Appeal start date, when published.
actual_completion_date	Actual completion date, when published.
locality	Locality, when published.
decision_agency	Decision agency, when published.
centroid.lat	Centroid / lat, when published.
centroid.lon	Centroid / lon, when published.
date_building_work_completed_under_previous_permission	Date building work completed under previous permission, when published.
url_planning_app	Url planning app, when published.
site_name	Site name, when published.
cil_liability	Cil liability, when published.
subdivision_of_building	Subdivision of building, when published.
appeal_status	Appeal status, when published.
appeal_decision	Appeal decision, when published.
pp_id	Pp id, when published.
reference_no_of_permission_being_relied_on	Reference no of permission being relied on, when published.
application_type_full	Application type full, when published.
id	Id, when published.
polygon	Polygon, when published.
source_status	Source status, when published.
record_id	Stable identifier for the source record.
url	Public source link when the website provides one.
application_details	Application details, when published.
additional_fields.name	Names of additional published fields, when present.
additional_fields.value	Their corresponding values in the same order.
application_details.lead_developer_company_name	Application details / lead developer company name, when published.
application_details.total_gia_gained	Application details / total gia gained, when published.
application_details.intended_completion_date	Application details / intended completion date, when published.
application_details.intended_commencement_date	Application details / intended commencement date, when published.
application_details.no_additional_bedrooms	Application details / no additional bedrooms, when published.
application_details.no_additional_bathrooms	Application details / no additional bathrooms, when published.

The complete result below is included for every mode. Text and lists are not shortened. These are examples from validation runs; the source can change.

Search planning application records — complete JSON result

{
  "result_type": "search",
  "input": "{\"keywords\": null}",
  "decision_conditions": [
    "PLANT NOISE (COMPLIANCE): The design and installation of the Air Source Heat Pump shall be such that when operating the cumulative noise level LAeq Tr arising from the proposed plant, measured or predicted at 1m from the facade of the nearest noise sensitive premises, shall not exceed a rating level of 42dBA.  The measurement and/or prediction of the noise should be carried out in accordance with the methodology contained within the Microgeneration Certification Scheme Planning Standards. \r\n\r\nREASON: To protect the amenity of neighbours."
  ],
  "actual_commencement_date": null,
  "decision_target_date": "24/03/2025",
  "lpa_name": "Islington",
  "centroid_northing": 185492,
  "last_updated": "2025-04-03T00:00:22.289Z",
  "development_type": null,
  "ward": null,
  "parking_details": {},
  "uprn": "5300000257",
  "last_date_consultation_comments": "01/03/2025",
  "decision": "Approved",
  "bo_system": "Agile APAS",
  "postcode": "N5 2BE",
  "secondary_street_name": null,
  "last_synced": "2025-04-03T04:35:47.322Z",
  "appeal_decision_date": null,
  "application_type": "All Other",
  "decision_date": null,
  "borough": "Islington",
  "wgs84_polygon.type": "Polygon",
  "wgs84_polygon.coordinates": [
    [
      [
        -0.093354,
        51.552828
      ],
      [
        -0.093355,
        51.552801
      ],
      [
        -0.093398,
        51.552801
      ],
      [
        -0.093397,
        51.552828
      ],
      [
        -0.093354,
        51.552828
      ]
    ]
  ],
  "lpa_app_no": "P2025/0271/FUL",
  "valid_date": "28/01/2025",
  "description": "Single storey rear extension and extension to existing first floor outrigger by 1 metre. Rear roof dormer, installation of new rooflights to side roof slope and other external alterations. Replace existing front UVPC windows for double-glazed timber with all other windows and rooflights to be triple glazed. Air Source Heat Pump to side elevation, removal of old solar panels and replace with new ones. Rear garden landscaping.",
  "centroid_easting": 532286,
  "site_number": "80",
  "lapsed_date": null,
  "date_building_work_started_under_previous_permission": null,
  "title_number": null,
  "decision_process": null,
  "epc_number": "2400-7993-0822-6609-5173",
  "street_name": "Aberdeen Park",
  "appeal_start_date": null,
  "actual_completion_date": null,
  "locality": null,
  "decision_agency": null,
  "centroid.lat": 51.552814,
  "centroid.lon": -0.093376,
  "date_building_work_completed_under_previous_permission": null,
  "url_planning_app": null,
  "site_name": null,
  "cil_liability": null,
  "subdivision_of_building": null,
  "appeal_status": null,
  "appeal_decision": null,
  "pp_id": "PP-13714934",
  "reference_no_of_permission_being_relied_on": null,
  "application_type_full": "Householder planning permission",
  "id": "Islington-P2025_0271_FUL",
  "polygon": null,
  "source_status": "Withdrawn",
  "status": "success",
  "record_id": "Islington-P2025_0271_FUL",
  "url": null,
  "application_details": {
    "lead_developer_company_name": "Councillor Caroline Russell",
    "total_gia_gained": 6,
    "intended_completion_date": "08/2026",
    "intended_commencement_date": "08/2025",
    "no_additional_bedrooms": 0,
    "no_additional_bathrooms": 2
  },
  "additional_fields.name": [],
  "additional_fields.value": []
}

Get planning application details — complete JSON result

{
  "result_type": "details",
  "input": "Islington-P2025_0271_FUL",
  "decision_conditions": [
    "PLANT NOISE (COMPLIANCE): The design and installation of the Air Source Heat Pump shall be such that when operating the cumulative noise level LAeq Tr arising from the proposed plant, measured or predicted at 1m from the facade of the nearest noise sensitive premises, shall not exceed a rating level of 42dBA.  The measurement and/or prediction of the noise should be carried out in accordance with the methodology contained within the Microgeneration Certification Scheme Planning Standards. \r\n\r\nREASON: To protect the amenity of neighbours."
  ],
  "actual_commencement_date": null,
  "decision_target_date": "24/03/2025",
  "lpa_name": "Islington",
  "centroid_northing": 185492,
  "last_updated": "2025-04-03T00:00:22.289Z",
  "development_type": null,
  "ward": null,
  "parking_details": {},
  "uprn": "5300000257",
  "application_details.lead_developer_company_name": "Councillor Caroline Russell",
  "application_details.total_gia_gained": 6,
  "application_details.intended_completion_date": "08/2026",
  "application_details.intended_commencement_date": "08/2025",
  "application_details.no_additional_bedrooms": 0,
  "application_details.no_additional_bathrooms": 2,
  "last_date_consultation_comments": "01/03/2025",
  "decision": "Approved",
  "bo_system": "Agile APAS",
  "postcode": "N5 2BE",
  "secondary_street_name": null,
  "last_synced": "2025-04-03T04:35:47.322Z",
  "appeal_decision_date": null,
  "application_type": "All Other",
  "decision_date": null,
  "borough": "Islington",
  "wgs84_polygon.type": "Polygon",
  "wgs84_polygon.coordinates": [
    [
      [
        -0.093354,
        51.552828
      ],
      [
        -0.093355,
        51.552801
      ],
      [
        -0.093398,
        51.552801
      ],
      [
        -0.093397,
        51.552828
      ],
      [
        -0.093354,
        51.552828
      ]
    ]
  ],
  "lpa_app_no": "P2025/0271/FUL",
  "valid_date": "28/01/2025",
  "description": "Single storey rear extension and extension to existing first floor outrigger by 1 metre. Rear roof dormer, installation of new rooflights to side roof slope and other external alterations. Replace existing front UVPC windows for double-glazed timber with all other windows and rooflights to be triple glazed. Air Source Heat Pump to side elevation, removal of old solar panels and replace with new ones. Rear garden landscaping.",
  "centroid_easting": 532286,
  "site_number": "80",
  "lapsed_date": null,
  "date_building_work_started_under_previous_permission": null,
  "title_number": null,
  "decision_process": null,
  "epc_number": "2400-7993-0822-6609-5173",
  "street_name": "Aberdeen Park",
  "appeal_start_date": null,
  "actual_completion_date": null,
  "locality": null,
  "decision_agency": null,
  "centroid.lat": 51.552814,
  "centroid.lon": -0.093376,
  "date_building_work_completed_under_previous_permission": null,
  "url_planning_app": null,
  "site_name": null,
  "cil_liability": null,
  "subdivision_of_building": null,
  "appeal_status": null,
  "appeal_decision": null,
  "pp_id": "PP-13714934",
  "reference_no_of_permission_being_relied_on": null,
  "application_type_full": "Householder planning permission",
  "id": "Islington-P2025_0271_FUL",
  "polygon": null,
  "source_status": "Withdrawn",
  "status": "success",
  "record_id": "Islington-P2025_0271_FUL",
  "url": null,
  "additional_fields.name": [],
  "additional_fields.value": []
}

Input settings ⚙️

Setting	What to enter
What to collect (mode)	Choose the information you need.
Maximum results per search or link (maxResults)	Collect up to this many saved results for each search or record link. Minimum: 1.
Keywords (keywords)	Words in the published application description. Leave empty to browse applications.
Planning application IDs (recordIds)	Enter one planning application id per line. Use this field in Details mode.

London Planning Applications scraping use cases 🎯

Find construction and development projects

Search the available permit or planning records and review their published work descriptions, locations and dates.

Track permit and application changes

Compare repeated exports by record ID or permit number. Keep revisions and application statuses separate when assessing changes.

Analyze local development activity

Group records by published location, application type, date or other available fields. Dataset coverage and reporting dates depend on the issuing authority.

Pricing and saved-result behavior 💰

See the Actor’s Pricing tab for the current rate. Under dataset-item pricing:

• Each saved record is one result. Lists and additional details attached to it do not create extra rows.
• A saved failed row is also one billable dataset item. This includes invalid inputs, unavailable records, empty searches and exhausted retries.
• At most one failed row is saved per input. Retry attempts do not create additional dataset rows.
• maxResults caps all saved rows for the input. Duplicate copies of the same input are processed once.

London Planning Applications scraper API and integrations 🔌

Replace $ACTOR_ID with the ID shown in the Actor’s API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","maxResults":10}'

Use Apify schedules for recurring collection, webhooks for completion notifications, and integrations for Google Sheets, Make, Zapier, cloud storage or your own application.

Reliability and public-data limits ⚠️

Temporary request failures are retried up to five total attempts. Invalid record inputs save a failed row without a website request. Confirmed missing records are not retried unnecessarily. If a later request fails, records already saved remain in the dataset. Normal pagination completion does not add a failed row. Collection stops after two consecutive pages return no new records. Configuration, data-saving or request-scheduling failures stop the run.

London Planning Applications controls the available records and fields. Search records can contain less information than a full public card. The Actor preserves published values and does not fill missing facts with estimates.

Frequently asked questions ❓

Do I need a London Planning Applications account?

No. This Actor collects the supported public information without your website login.

Which search filters can I use?

The input form supports keywords. Only the displayed filters are supported.

How many records can I collect?

Set maxResults to the maximum saved rows you want for each input. The minimum is 1. Collection can finish earlier when the source runs out of results or stops returning new records.

Why are some fields empty?

The source may not publish a value for that record or mode. Optional information remains empty.

Can I export all the fields?

Yes. All returned fields are included in one dataset view. Nested lists remain attached to their parent record.

Support 🛟

For a reproducible issue, share the run ID, selected mode and a safe public example through the Actor’s support channel. Keep tokens, passwords and proxy credentials private.