# Victoria Building Permits (Australia) - Data & Suburb Trends (`mollydancer/victoria-building-permits`) Actor

Every building permit issued in Victoria, Australia: cost, work type, building class, suburb, council and builder location. Filter or get suburb trends. Official open data (CC BY 4.0).

- **URL**: https://apify.com/mollydancer/victoria-building-permits.md
- **Developed by:** [MollyDancer](https://apify.com/mollydancer) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 permits

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

## Victoria Building Permits (Australia) - Data & Suburb Trends

Search **every building permit issued in Victoria, Australia** and get clean, ready-to-use data: cost of works, work type, building class, street, suburb, postcode, council, new dwellings, floor area, building materials and the builder's location.

Or switch to **Summary mode** and get one row per suburb, postcode, council or month — number of permits, total and median value, new dwellings, new builds vs extensions vs demolitions.

The data comes from the **Building and Plumbing Commission (formerly the Victorian Building Authority)**, which collects a record from building surveyors for every permit issued in the state. The official files are large spreadsheets in an old Excel format with 36 coded columns. This Actor does the cleaning for you.

### What you can do with it

- **Building product suppliers and manufacturers** (windows, roofing, frames, pools, solar, landscaping): see which suburbs and councils have the most new builds and extensions, and how much is being spent.
- **Builders and developers**: see where competitors are active, typical costs per project type and suburb, and multi-unit developments (`minNewDwellings`).
- **Property investors and analysts**: track construction activity and new housing supply by suburb, month by month.
- **Councils, consultants, researchers and journalists**: pull clean, consistent permit data without wrangling spreadsheets.
- **AI agents**: works through the Apify MCP server, so an assistant can answer "how many new houses were approved in Tarneit this year?"

### Data coverage

| | |
|---|---|
| Area | All of Victoria, Australia (82 councils) |
| Current coverage | January 2026 – September 2026 (77,600+ permits) |
| Refresh | Updated whenever the Building and Plumbing Commission publishes a new file |
| Volume | Around 8,500 permits per month |

Check the `datasetCoverage` field in each run's `OUTPUT` record for the exact period included.

**Privacy:** the source data contains **no owner names, no builder names and no house numbers** — only the street, suburb and postcode. Nothing personal is added.

### Input examples

**New houses over $500k in Wyndham, most expensive first**

```json
{
  "councils": ["Wyndham"],
  "buildingClasses": ["1a"],
  "workTypes": ["New building"],
  "minCost": 500000,
  "sortBy": "costDesc"
}
```

**Pools, decks and fences in the western suburbs since July**

```json
{
  "regions": ["Western"],
  "buildingClasses": ["10b"],
  "dateFrom": "2026-07-01"
}
```

**Building activity by suburb in Casey (summary)**

```json
{
  "outputMode": "summary",
  "summaryGroupBy": "suburb",
  "councils": ["Casey"]
}
```

#### Filters

`councils`, `suburbs`, `postcodes`, `regions` (e.g. Metropolitan, Rural, Outer Melbourne, Gippsland, South Eastern), `streetContains`, `workTypes`, `buildingUses`, `buildingClasses`, `ownershipSectors`, `minNewDwellings`, `solarHotWater`, `rainwaterTank`, `minCost`, `maxCost`, `dateFrom`, `dateTo`, `sortBy`, `maxResults`.

Text filters ignore upper/lower case. Leave a filter empty to include everything.

### Output examples

**Permit row**

```json
{
  "permitDate": "2026-09-30",
  "applicationDate": "2026-09-21",
  "workType": "Other",
  "buildingUse": "Domestic",
  "buildingClass": "10b",
  "buildingClassDescription": "Fence, swimming pool, retaining wall, deck or mast",
  "costOfWorks": 72400,
  "street": "Primrose Place",
  "suburb": "Tarneit",
  "postcode": "3029",
  "council": "Wyndham",
  "region": "Metropolitan",
  "subRegion": "Outer Melbourne",
  "metroArea": "South Western",
  "newDwellings": 0,
  "builderSuburb": "Bacchus Marsh",
  "builderState": "VIC",
  "ownershipSector": "Private",
  "recordId": "44f3d91a5ea2973d"
}
```

Each permit also includes application date, project total cost, levy paid, allotment area, new floor area, storeys, existing / new / demolished dwellings, floor, frame, roof and wall materials, solar hot water and rainwater tank flags, and the builder's postcode.

**Summary row** (`summaryGroupBy: "month"`)

```json
{
  "groupBy": "month",
  "group": "2026-01",
  "permits": 344,
  "totalCostOfWorks": 115869776,
  "averageCostOfWorks": 336831,
  "medianCostOfWorks": 311520,
  "newDwellings": 221,
  "newBuildings": 262,
  "extensions": 20,
  "alterations": 32,
  "demolitions": 12
}
```

Download results as JSON, CSV, Excel or HTML, or connect them to Google Sheets, Make, Zapier or your own code through the Apify API.

### Pricing

Pay only for what you get:

- **$5 per 1,000 permits** returned
- **$0.03 per summary row**

A summary of every suburb in a typical council (around 25 suburbs) costs about $0.75; the largest councils cost just over $2. Set a maximum cost per run in Apify Console and the Actor stops at exactly that amount. Users on Apify's free plan get a preview (first 25 permits or 5 summary rows).

### Good to know

- **Months in summaries are reporting months** — the month the permit was reported to the Commission. A few permits are reported months after they were issued, so `firstPermitDate` in a summary can be earlier than the month itself. Use `dateFrom` / `dateTo` to filter by the actual permit date.
- **Costs are as declared on the permit**, not final build costs.
- **Large developments** can appear as one permit covering many dwellings (check `newDwellings`) or as several staged permits (`stageNumber`).
- Rows that are identical in every column are kept: they are usually separate permits for identical dwellings in the same development.

### Data source and licence

Source: Building and Plumbing Commission (Victoria), *Building Permit Activity Data*, published on [DataVic](https://discover.data.vic.gov.au/dataset/building-permit-activity-data) under the [Creative Commons Attribution 4.0 International licence](https://creativecommons.org/licenses/by/4.0/). This Actor cleans and restructures the data (decoding codes, standardising state names and building classes, converting dates). Every row carries an attribution line.

This Actor is independent and is **not affiliated with or endorsed by** the Building and Plumbing Commission or the Victorian Government. The Commission notes the data is supplied by building surveyors and is not warranted to be accurate or complete. Verify important details with the relevant council or building surveyor before relying on them.

# Actor input Schema

## `outputMode` (type: `string`):

Individual permits (one row per permit), or a summary (one row per suburb, council, month, etc.) with counts and total value.

## `summaryGroupBy` (type: `string`):

Only used when 'Summary / trends' is selected.

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

Council (municipality) names, e.g. Wyndham, Casey, Melbourne, Greater Geelong. Leave empty for all of Victoria.

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

Suburb names, e.g. Werribee, Point Cook, Tarneit.

## `postcodes` (type: `array`):

4-digit postcodes, e.g. 3030.

## `regions` (type: `array`):

Region or sub-region names, e.g. Metropolitan, Rural, Outer Melbourne, Inner Melbourne, Gippsland, Western, South Eastern.

## `streetContains` (type: `string`):

Optional text to match in the street name, e.g. 'Hoppers'.

## `workTypes` (type: `array`):

Leave empty for all work types.

## `buildingUses` (type: `array`):

What the building is used for. Leave empty for all uses.

## `buildingClasses` (type: `array`):

National Construction Code building class. 1a = houses/townhouses, 2 = apartments, 10a = sheds/garages/carports, 10b = pools/fences/decks.

## `ownershipSectors` (type: `array`):

Who owns the project. Leave empty for all.

## `minNewDwellings` (type: `integer`):

e.g. 2 to find multi-unit developments.

## `solarHotWater` (type: `boolean`):

Tick to keep only permits reporting solar hot water. Leave unset for all.

## `rainwaterTank` (type: `boolean`):

Tick to keep only permits reporting a rainwater tank. Leave unset for all.

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

Only include permits with at least this cost of works, in Australian dollars.

## `maxCost` (type: `integer`):

Only include permits with at most this cost of works, in Australian dollars.

## `dateFrom` (type: `string`):

YYYY-MM-DD

## `dateTo` (type: `string`):

YYYY-MM-DD (inclusive)

## `sortBy` (type: `string`):

Order of the permit rows. Ignored in summary mode.

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

Stop after this many rows. You are charged per row returned.

## Actor input object example

```json
{
  "outputMode": "permits",
  "summaryGroupBy": "suburb",
  "sortBy": "permitDateDesc",
  "maxResults": 100
}
```

# Actor output Schema

## `permits` (type: `string`):

One row per building permit (when 'Individual permits' is selected).

## `summary` (type: `string`):

One row per suburb, council, month etc. (when 'Summary / trends' is selected).

## `runSummary` (type: `string`):

How many permits matched, rows returned and the data coverage period.

# 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 = {
    "maxResults": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("mollydancer/victoria-building-permits").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 = { "maxResults": 100 }

# Run the Actor and wait for it to finish
run = client.actor("mollydancer/victoria-building-permits").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 '{
  "maxResults": 100
}' |
apify call mollydancer/victoria-building-permits --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mollydancer/victoria-building-permits"
        }
    }
}
```

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/8pkj4Y5jTArVmzaKb/builds/fgotLOIdBmba3xTeT/openapi.json
