# NSW Planning Portal Development Applications Scraper (`talcoe/nsw-planning-portal`) Actor

Extract NSW development applications from the Planning Portal, filtered by council, status, suburb, lodgement window and minimum cost, billed per result.

- **URL**: https://apify.com/talcoe/nsw-planning-portal.md
- **Developed by:** [M Usama](https://apify.com/talcoe) (community)
- **Categories:** Lead generation, Real estate, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does NSW Planning Portal Development Applications Scraper do?

It returns development applications (DAs, modifications and reviews) lodged through the NSW Planning Portal, across every participating NSW council. Each record has the council, council application number, status, address, declared cost of development, lodgement and determination dates, development types, new dwellings, storeys and coordinates. Filter by lodgement window, council, status, suburb and minimum cost so runs stay small. Pricing is per result.

### Data source

The public Online DA Data API published by the NSW Department of Planning, Housing and Infrastructure, updated daily by the portal.

### Why use it?

- Find new construction, subdivision and commercial projects the week they are lodged, with a declared cost to rank them.
- Build lead lists for builders, certifiers, surveyors, trades and suppliers by suburb or council.
- Monitor determinations and status changes in the councils you cover.
- Replace manual searching of council tracking pages and the portal's search form.

### How to use it

1. Open the Actor and set the filters.
2. Click Start. Download results as JSON, CSV or Excel, or read them through the API.
3. Add a Schedule and an Integration (Slack, Google Sheets, webhook) to get new records automatically.

### Input

| Field | Description |
|---|---|
| `lodgedWithinDays` | Only applications lodged in the last N days. Default 7. |
| `councils` | Exact council names, for example `Northern Beaches Council`. Empty means all of NSW. |
| `applicationStatuses` | Under Assessment, On Exhibition, Additional Information Requested, Determined, Withdrawn, Rejected, Cancelled. Empty means all. |
| `minCost` | Minimum declared cost of development in AUD. |
| `suburbs` | Suburb names such as `BONDI`. Applied after download, so pair with a council for speed. |
| `maxResults` | Hard stop for the run. You are billed per result, so this caps the cost. |
| `proxyConfiguration` | Apify proxy is recommended for larger runs. |

Example input:

```json
{
    "lodgedWithinDays": 30,
    "councils": ["Northern Beaches Council"],
    "applicationStatuses": ["Under Assessment"],
    "minCost": 500000,
    "maxResults": 100
}
```

### Output

Every record has the same shape. Results are returned newest update first.

```json
{
    "id": "PAN-684029",
    "councilApplicationNumber": "DA.2026.0569",
    "council": "Queanbeyan-Palerang Regional Council",
    "status": "Under Assessment",
    "applicationType": "Development Application",
    "address": "41A RYRIE STREET BRAIDWOOD 2622",
    "suburb": "BRAIDWOOD",
    "postcode": "2622",
    "costOfDevelopment": 88500,
    "lodgementDate": "2026-10-15",
    "determinationDate": null,
    "submissionDate": "2026-10-15",
    "lastUpdated": "2026-10-15T21:07:10",
    "developmentTypes": ["Erection of a new structure", "Transport depot", "Transport Infrastructure"],
    "latitude": -35.44455838,
    "longitude": 149.797841433,
    "lots": ["21/DP848206"],
    "scrapedAt": "2026-10-16T08:29:30.147Z"
}
```

| Field | Meaning |
|---|---|
| `id` | Planning Portal application number, safe for deduplication between runs |
| `councilApplicationNumber` | The council's own reference |
| `council` | Consent authority council |
| `status` | Current portal status |
| `costOfDevelopment` | Cost declared by the applicant, in AUD |
| `lodgementDate`, `determinationDate` | ISO dates |
| `lastUpdated` | Last portal update, local NSW time with no zone |
| `developmentTypes` | Categories the applicant selected |
| `determinationAuthority` | Who decided the application, when known |
| `locations`, `lots` | All addresses and lot/plan references on the application |

### Pricing

Pay per event: a small fee when a run starts, then a fixed price per result returned. You only pay for records that pass your filters. Set `maxResults` to cap any run.

### Limitations

- The public API does not publish applicant or owner names, so they are not included.
- Only applications lodged through the NSW Planning Portal are covered. Councils that still take paper or their own online forms may not appear.
- Council, status, cost and lodgement date filters are applied by the portal. Suburb is applied after download.
- Cost is the applicant's declared figure and can be zero or missing.

### FAQ

**Is this legal?** The Actor reads data the NSW government publishes openly for any visitor without a login and stores only application details published for that purpose. You are responsible for how you use the data.

**Something is missing or broken?** Open an issue in the Issues tab; response time is usually under a day.

# Actor input Schema

## `lodgedWithinDays` (type: `integer`):

Only applications lodged in this window. Larger windows return more records.

## `councils` (type: `array`):

Exact council names as the portal publishes them, for example Northern Beaches Council or Blacktown City Council. Leave empty for all of NSW.

## `applicationStatuses` (type: `array`):

Keep only these statuses. Leave empty for all.

## `minCost` (type: `integer`):

Only applications with a declared cost at or above this value. 0 means no minimum.

## `suburbs` (type: `array`):

Keep only these suburbs, for example BONDI. Matched after download, so combine with a council for faster runs.

## `maxResults` (type: `integer`):

Hard stop for the run. You are billed per result, so this caps the cost.

## `proxyConfiguration` (type: `object`):

Apify proxy is recommended for larger runs.

## Actor input object example

```json
{
  "lodgedWithinDays": 7,
  "councils": [],
  "applicationStatuses": [],
  "minCost": 0,
  "suburbs": [],
  "maxResults": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "lodgedWithinDays": 7,
    "councils": [],
    "applicationStatuses": [],
    "minCost": 0,
    "suburbs": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("talcoe/nsw-planning-portal").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "lodgedWithinDays": 7,
    "councils": [],
    "applicationStatuses": [],
    "minCost": 0,
    "suburbs": [],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("talcoe/nsw-planning-portal").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "lodgedWithinDays": 7,
  "councils": [],
  "applicationStatuses": [],
  "minCost": 0,
  "suburbs": [],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call talcoe/nsw-planning-portal --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,talcoe/nsw-planning-portal"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/GvYVl4n94eNeABtvP/builds/RIe8KXhStTcUMGR1Q/openapi.json