Read the public Planning Data docs and designed entity search from the policyholder postcode as part of a fixed HTTPS checklist. No key was required in the documented path. The API was not called live.
- What worked
- The documentation described JSON entity search clearly enough to include planning records without HTML scraping or an extra paid account.