Building Permits API

ใบอนุญาตก่อสร้างและคำขอวางแผนสำหรับฝรั่งเศส NSW ออสเตรเลีย และ Far North NZ

เซิร์ฟเวอร์ MCP แบบโฮสต์

npx add-mcp 'https://mcp.apify.com/?tools=gaelasao/planning-data-au-nz-fr'

ติดตั้งลง Claude Code, Codex, Cursor และอื่นๆ

เอกสาร

Building Permits API: US Construction Leads, France, NSW, NZ (`gaelasao/planning-data-au-nz-fr`) Actor

Construction leads from building permits and planning applications: 12 US cities (NYC, Los Angeles, Chicago, Dallas, Seattle, Austin, Orlando, New Orleans, Cincinnati, Mesa, Baton Rouge, Montgomery County) with value and contractor; France permis de construire; NSW development applications.

URL: https://apify.com/gaelasao/planning-data-au-nz-fr.md
Developed by: Gaël GERARD (community)
Categories: Real estate, Lead generation
Stats: 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
User rating: No ratings yet

Pricing

from $4.00 / 1,000 planning records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 section below.

Each client library has reference documentation the quickstart does not restate: JavaScript/TypeScript (npm install apify-client) and Python (pip install apify-client).

README

Construction leads from official building permits. Get the permits a city issued in your ZIP codes, with the declared project value and, where the city publishes it, the contractor's business name: 12 US cities and counties (New York City, Los Angeles, Chicago, Dallas, Seattle, Austin, Orlando, New Orleans, Cincinnati, Mesa, Baton Rouge and Montgomery County, Maryland). The same Actor downloads building permits and planning applications from France, NSW Australia and Far North New Zealand.

A permit is on record weeks before the work starts. Suppliers, subcontractors, solar and roofing companies, insurers and PropTech teams use it to find new projects street by street and to see which contractors are busy. Filter by ZIP code or keyword (solar, roof, ADU, pool...), export as JSON, CSV or Excel, or schedule a weekly run to get only the new permits. Each result keeps its original reference, dates and source, so you can check the record behind the numbers.

Try it now: the form opens on the United States (New York City, last 90 days, 10 permits) for about $0.05, plus the $0.00005 start event at 512 MB. Set your maximum cost per run before starting (the default is $5). No monthly Actor rental and no separate source API key. Your Apify account and credits are required.

Real output for 8 US building permits from New York City, Chicago, Los Angeles, Seattle and Austin: permit number, type, work description, ZIP code, project value, contractor and issue date

Ready-to-run examples

Choose the data you need, open the example and try its preset. Each starts with 10 results, a $0.10 spending limit and the last 90 days (France: the 90 days up to the end of the latest monthly SDES file). Adjust the area or dates in your own copy.

Example	What is already configured
New York City: building permits	DOB NOW permits issued in the last 90 days, with project value and contractor
Los Angeles: building permits	LADBS permits issued in the last 90 days, with project value
Chicago: building permits	Permits issued in the last 90 days, with reported cost and contractor
Dallas: building permits	Permits issued in the last 90 days, filter by ZIP code
Austin: building permits	Permits issued in the last 90 days, with contractor and a link to the city permit page
Solar panel permits	Solar installations in Austin, Orlando and New York City (keyword solar)
Roofing permits	Reroof permits in Los Angeles, Orlando and Cincinnati (keyword roof)
France : permis de construire de logements	Autorisations SDES de logements, France entière
France: non-residential building permits	SDES non-residential authorisations
NSW: development applications	NSW Planning Portal, all councils

Pour la France : choisissez logements, locaux non résidentiels, aménagement ou démolition. Vous pouvez ensuite filtrer par département ou code INSEE de commune et télécharger les résultats en CSV. Chaque ligne décrit le projet (nature, destination, logements, surface créée). Quand le demandeur est une personne morale, sa dénomination, son SIREN, son SIRET et son code APE sont fournis. Les autorisations SDES sont publiées mensuellement : sans date, la période se termine à la fin de couverture du dernier fichier publié.

What can you do with building permit data?

Find construction leads. In US cities, filter by ZIP code or keyword and sort by project value to see what is being built, and by whom when the city publishes the contractor.
Follow projects in your area. Review applications or issued authorisations for a council, French department or commune.
Research development activity. Compare the records available for a territory and period before adding them to your own analysis.
Keep a repeatable workflow. Use the same filters and output fields across supported sources, then export to a spreadsheet or call the Actor through the Apify API.

The official source data remains publicly available from its publishers. You pay for collection, filters and a consistent export, rather than exclusive access to those records. This is useful when you want to repeat a query or connect the data to an existing workflow without maintaining a separate integration for each source.

Which building permits and planning applications are covered?

Country	Available records	Coverage and freshness
United States	Issued building permits from the open-data portals of New York City (DOB NOW: Build), Los Angeles (LADBS), Chicago, Dallas, Seattle (SDCI), Austin, Orlando, New Orleans, Cincinnati, Mesa (Arizona), East Baton Rouge Parish and Montgomery County (Maryland, residential and commercial)	These 12 areas only, not nationwide. The portals are updated daily or every few days; on 25 October 2026 most data ran to 22–24 October.
Australia	NSW Planning Portal planning and complying-development applications, including modifications	NSW only. Source catalogue advertises daily updates. The tracker does not provide a per-record update timestamp.
New Zealand	Far North building applications published from Pathway	Far North District only. Publisher advertises daily refresh. Selected types/statuses; no street-address field. Property points are provided.
France	SDES housing, non-residential, development (PA) and demolition (PD) authorisations	Selected issued authorisations since 2013. Monthly publication; not a live feed of all pending applications.

Coverage is specific to the sources above. Country names identify where the data comes from. The COVERAGE report gives the sources and publication snapshots used by your run; SUMMARY explains whether the run reached a limit or finished its query.

How to get your first results

Open a ready-to-run example above, or use the Input form to choose a country.
Set the area: a city or county and optional ZIP codes or keywords for the US, an INSEE commune or department code for France, or an exact council name for NSW. New Zealand uses the Far North dataset.
Choose your dates. Start with 10 results and a $0.10 maximum run cost.
Run the Actor, then download JSON from the dataset or choose CSV for spreadsheets in the output menu. Read the summary before treating the export as a complete query.

Omitting dates uses the 90 days ending today (UTC) for the US, NSW and Far North. France is published monthly, so its period ends at the coverage end of the latest SDES file: 31 August 2026 for the file published on 29 September 2026. For repeatable research, set dates explicitly. Apify schedules can run the same input again; stable record IDs help you remove duplicates in your own workflow.

Examples

United States: New York City permits in one ZIP code

{
  "country": "US",
  "sourceIds": ["us-nyc-dob"],
  "zipCodes": ["10001"],
  "maxResults": 10
}

United States: Dallas permits in two ZIP codes

{
  "country": "US",
  "sourceIds": ["us-dallas-building"],
  "zipCodes": ["75201", "75204"],
  "maxResults": 25
}

United States: solar permits in Seattle and Austin

{
  "country": "US",
  "sourceIds": ["us-seattle-building", "us-austin-building"],
  "keywords": ["solar"],
  "maxResults": 50
}

maxResults is shared across sources in order: for a fixed number of rows per city, run one city at a time.

France: housing authorisations in Rhône

{
  "country": "FR",
  "sourceIds": ["fr-sdes-housing"],
  "departmentCodes": ["69"],
  "maxResults": 10
}

Australia: NSW applications in City of Sydney

{
  "country": "AU",
  "councils": ["Council of the City of Sydney"],
  "maxResults": 10
}

New Zealand: Far North building applications

{
  "country": "NZ",
  "maxResults": 10
}

These examples use the default period: the last 90 days, or for France the 90 days up to the latest SDES coverage end. Add dateFrom and dateTo in YYYY-MM-DD format when you need a fixed research period. Leave maxRequests out: the Actor sizes source requests from maxResults.

What does a result contain?

Results include the application, permit or authorisation reference, published type and status, available dates and the responsible authority. NSW and Far North provide the publisher's project description. For France, the Actor composes a short French description from SDES codes (project nature, main destination, dwellings and floor area created). When the French applicant is a legal entity, records also carry its name, SIREN, SIRET, NAF (APE) code, legal category, postal code and locality. Address and location fields depend on the source. Each record also includes its source link, attribution, licence information and collection date.

United States. Each permit carries the city's permit number, type, status, work description, address, ZIP code, coordinates and issue date, plus the application date (in New York City, the approval date). metrics adds project_value_usd (the value declared to the city), contractor_business_name, housing_units, permit_subtype and, in Austin and Seattle, permit_url, a link to the city's permit page. What each city publishes differs. Share of rows with each field in our 300-row checks of 24 and 25 October 2026:

City or county	Source ID	Project value	Contractor	ZIP code
New York City	`us-nyc-dob`	100%	100%	100%
Los Angeles	`us-la-building`	100%	Not in the source	100%
Chicago	`us-chicago-building`	90%	58%	Not in the source
Dallas	`us-dallas-building`	Rarely filled	Rarely filled	100%
Seattle	`us-seattle-building`	100%	8%	92%
Austin	`us-austin-building`	23% (building permits only, not trade permits)	95%	100%
Orlando	`us-orlando-building`	89%	85%	Not in the source
New Orleans	`us-new-orleans-building`	83%	32%	Not in the source
Cincinnati	`us-cincinnati-building`	95%	96%	99%
Mesa, Arizona	`us-mesa-building`	81%	41%	Not in the source
East Baton Rouge Parish	`us-baton-rouge-building`	66%	58%	100%
Montgomery County, Maryland	`us-montgomery-md-residential`, `us-montgomery-md-commercial`	95–100%	Not in the source	98–100%

Contractor fields keep business names only. When a city mixes a person and a firm in one field, only the firm is kept. Names of individual owners and contacts are not collected, nor are phone numbers or emails.

France. A real extract for the Rhône department, with the applicant company and its SIREN:

Real output for 8 housing authorisations in Rhône, France: permit type, status, dwellings, floor area, applicant company with SIREN and dates

The Output tab has a general view plus views for United States permits, France SDES and Far North NZ. France shows the project description, status, commune, postal code, address, dates, applicant company and SIREN, with housing and floor-area measures; PA/PD rows describe the land area only. Far North shows application details and property coordinates. Its coordinates identify a property point, not a verified building entrance. Use the view that matches your source, then download the full JSON when you need every field.

Here is an extract from a real NSW result collected on 13 October 2026. The full output contains additional provenance and quality fields.

{
  "country": "AU",
  "source_id": "au-nsw-tracker",
  "authority_name": "Council of the City of Sydney",
  "reference": "CDC-282727",
  "description": "Restaurant or cafe,Alterations or additions to an existing building or structure",
  "address": "305 BOTANY ROAD ZETLAND 2017",
  "submitted_date": "2026-10-09"
}

For spreadsheet use, the CSV for spreadsheets output escapes quotes and prefixes formula-like text with an apostrophe. This protects text starting with =, +, - or @ from being treated as a formula. JSON preserves the original text. The CSV starts with a UTF-8 byte-order mark so that Excel shows accents. It includes the INSEE commune code (authority_id), postal code, commune, category, normalized status, dwellings, floor and land areas, the Far North property ID, the French applicant fields and, for the US, project value, contractor, housing units, permit subtype and permit link. Excel can drop leading zeros from codes such as 01034: import the file with Data → From Text/CSV and set those columns to Text, or use JSON. JSON contains the full record, including provenance and quality fields.

Missing values stay null. Descriptions remain in the original language. French state codes are kept in raw_status; normalized_status follows the SDES dictionary (approved, cancelled, works_started, works_completed). US statuses map to approved, works_completed, expired, cancelled, refused or withdrawn when the city's wording is clear, and stay in raw_status as published. Each Far North result is an application/property pair: an application spanning several properties can produce several rows.

How do the filters work?

One country per run; the same input/output contract serves each country.
France: INSEE commune and department codes, plus the four source categories.
US: ZIP codes (not for Chicago, Orlando, New Orleans or Mesa, whose datasets have none) and keywords in the work description, both applied by the city portal. Dallas publishes issue dates only, as text, so a Dallas period can span at most 400 days.
NSW: exact council display names. AU/NZ also support keyword substrings in project/type fields.
Date meaning matters: France and the US default to issued dates; AU/NZ to submission dates. US cities also support application dates, except New York City, which supports approval dates instead. France also supports submission dates within its authorisation dataset; NZ also supports decision dates.
maxResults caps output records. Leave maxRequests empty: the Actor sizes source requests from maxResults (France pages hold 100 rows; NSW, Far North and US pages up to 1,000). Responses are limited to 8 MiB each and 64 MiB in total per run.
A run that stops at a limit (results, requests, maximum cost or timeout) still succeeds. Its status message names the limit and SUMMARY.limit_reached records it. Only a run that delivers no record because of a source error fails. No cap promises an exhaustive national dataset.

An issued permit establishes an authorisation, rather than the start of construction. Source coverage and publication delays matter when interpreting activity or comparing territories.

How much does the Building Permits API cost?

The launch price is $5 per 1,000 returned records ($0.005 per row), plus Apify's standard $0.00005 Actor start event at the default 512 MB memory. Platform usage is included in this Actor's price.

Returned records	Price at 512 MB	Suggested spending limit
10	$0.05005	$0.10
100	$0.50005	$0.51
1,000	$5.00005	$5.01

The spending limit caps charges; it does not guarantee a result count. When a run reaches it, the run keeps the rows it paid for, ends successfully and its status message names the limit, for example “Stopped by your maximum cost per run ($0.10) after 19 records.” A Far North row counts as one application/property pair. Every run is charged for the rows it returns, including records returned by an earlier run.

Large exports take time. France returns at most 100 rows per source request, about 4–5 seconds each: 1,000 French rows take about one minute, 2,000 about two minutes. NSW, Far North and the US portals return up to 1,000 rows per request. Use a run timeout of at least 600 seconds for exports above 1,000 rows. If the timeout approaches, the Actor stops collecting early, keeps the delivered rows and still saves SUMMARY and the CSV.

There is no monthly rental fee for this Actor. Your Apify account's plan and available credits still apply. The current Pricing tab governs charges. Set a maximum run cost before starting; the Actor checks the remaining result budget before collecting or storing further rows.

Frequently asked questions

Can I get permis de construire data for France?

Yes. The France sources are the SDES Sitadel files for housing, non-residential buildings, development (PA) and demolition (PD) authorisations. Filter with department or INSEE commune codes. These are selected issued authorisations, published monthly; use the source snapshot to check the reporting period.

Does it cover building permits in the United States?

Yes, for 12 cities and counties: New York City, Los Angeles, Chicago, Dallas, Seattle, Austin, Orlando, New Orleans, Cincinnati, Mesa (Arizona), East Baton Rouge Parish and Montgomery County (Maryland), from each one's open-data portal. Choose country: "US", pick the city in sourceIds (see the table above) and filter by ZIP code or keywords. Other US cities are not covered yet: tell us which one you need on the Issues tab.

Can I get contractor names and project values for US permits?

Yes, where the city publishes them: the project value is in metrics.project_value_usd and the contractor's business name in metrics.contractor_business_name (see the table above for each city). They are the values declared to the city. Names of individuals, phone numbers and emails are not collected.

Does it cover all of Australia and New Zealand?

Australian coverage is NSW. New Zealand coverage is Far North District. Additional territories will be listed here when a supported source is available.

Can I get applicant companies, contacts or Far North street addresses?

For France, companies yes. When the SDES file identifies the applicant as a legal entity found in Sirène, each record carries its name, SIREN, SIRET, NAF (APE) code, legal category, postal code and locality. Natural persons, sole traders (legal category 1000) and groupings of natural persons are never exported, including their postal code. A family property company (SCI) name can still identify a household: treat it as personal data under the GDPR. No email address or phone number is provided. Far North provides property points, with no street-address field in the source used by this Actor.

Can I connect it to my own application?

Yes. Use gaelasao/planning-data-au-nz-fr through the Apify API. Each run gives you a dataset of records and links to its SUMMARY and COVERAGE reports. Run one country at a time; the output field names remain consistent across sources.

How do I call it from a script?

Set your Apify token in the APIFY_TOKEN environment variable, then send your filters as JSON. This example returns up to three France records in one HTTP response:

curl --fail-with-body --request POST \
  'https://api.apify.com/v2/acts/gaelasao~planning-data-au-nz-fr/run-sync-get-dataset-items?memory=512&timeout=180&maxTotalChargeUsd=0.1&format=json' \
  --header "Authorization: Bearer $APIFY_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"country":"FR","sourceIds":["fr-sdes-housing"],"departmentCodes":["69"],"maxResults":3}'

Use US with a city in sourceIds, AU with an exact NSW council name or NZ for Far North, as shown in the examples above. Leave unused filters out of your request. Optional lists, dates and numeric limits also accept null. For country and dateField, use a listed value or omit the field to use its default. Do not put your token in a shared URL or source file.

If you adapt Apify's generated Python example, remove unset None values before calling the Actor:

run_input = {key: value for key, value in run_input.items() if value is not None}

With maxTotalChargeUsd=0.1 as in this example, a run allows up to 19 records plus the start event at this price. For up to 100 records, set maxResults to 100 and a run budget of $0.51; for 1,000, use $5.01 and timeout=600. The result limit and spending limit are separate, and a source can return fewer records. If the budget runs out first, the run still succeeds with the rows it paid for and its status message says so. See the synchronous API endpoint for longer-running requests.

Can I use it through an MCP connector?

Yes. Apify hosts this Actor and exposes it through its MCP server. In a compatible MCP client, connect to:

https://mcp.apify.com?tools=actors,docs,gaelasao/planning-data-au-nz-fr

Authenticate with your own Apify account using the client’s supported login flow. No additional server or source login is needed. Ask the client to run this Actor for one country with maxResults: 10 and set the run spending limit to $0.10. Spending limits are run options, not input fields. The client must fetch the dataset after the run; starting an Actor alone returns run and storage identifiers. Read the returned SUMMARY as well as the rows.

Can I repeat the query or send the results to another tool?

Save your input as an Apify task, then use Apify’s schedules or integrations to repeat it and retrieve the output. Daily runs can be useful for the US cities, NSW and Far North; France is published monthly. Choose a frequency that matches the source. Keep record_id in your destination to recognise previously collected rows. Repeated rows are still charged on each run. This version does not return a change-only feed or send alerts by itself.

Why did my run return fewer results than expected?

Check the area, the meaning of your date filter and the source publication period. Then read the run's status message and SUMMARY: they name the limit that stopped the run (result cap, request cap, maximum cost or timeout) and list source errors. For France, a period without dateTo ends at the latest SDES coverage end; recent months are not published yet. A query finishing successfully does not independently verify the publisher's completeness.

Are source text and statuses cleaned up?

French addresses and communes often reach SDES with broken accents (repeated UTF-8 encoding, shown for example as CHAÃÂZERY instead of CHÉZERY): about a quarter of French rows in our checks. The Actor repairs them, keeps the publisher's original text in source_text_raw and adds the warning text_encoding_repaired. Rare ambiguous cases stay unchanged and carry text_encoding_suspect. Other source text and status codes are retained, and missing values stay empty. This version retrieves source records as they are available at run time; it has no shared historical change log.

Attribution and data rights

This Actor selects fields, normalises schemas and filters records. Source text remains unchanged where available. It is not affiliated with or endorsed by the publishers.

United States: New York City Department of Buildings via NYC Open Data (terms of use); City of Chicago Data Portal (terms of use); Los Angeles Department of Building and Safety via Los Angeles Open Data; City of Austin, public domain as declared by the publisher; City of Seattle, public domain as declared by the publisher; City of Dallas via Dallas OpenData; City of Orlando via Orlando Open Data; City of New Orleans, Department of Safety and Permits, CC0 1.0; City of Cincinnati, public domain as declared by the publisher; City of Mesa via Mesa Open Data; East Baton Rouge Parish via Open Data BR, public domain as declared; Montgomery County, Maryland, Department of Permitting Services, public domain as declared (residential, commercial).
France: SDES, base Sitadel, Licence Ouverte as declared by the official dataset. Publication dates and source links are retained.
New Zealand: Far North District Council, published building layer, CC BY 4.0.
NSW: © State of New South Wales and Department of Planning, Housing and Infrastructure. The Portal copyright notice identifies CC BY 4.0 for department material, subject to its stated exclusions. The Actor retrieves tracker metadata, not application documents, third-party plans, images or logos. Original application tracker.

Publisher data is provided without a guarantee of accuracy, completeness or continued availability. Preserve source attribution, applicable licence terms and the notices accompanying any downstream reuse.

Support

For an input or source problem, open an issue on this Actor’s Issues tab with the run ID, source ID and the filters you used. Those details help us reproduce the problem and check the source response. Do not include API tokens or private data.

If the export helped with your work, an honest review on Apify helps other users decide whether it fits their needs. Tell us what you used it for and what could be better.

Changelog

This Actor's version history is a separate document: https://apify.com/gaelasao/planning-data-au-nz-fr/changelog.md

Actor input Schema

`country` (type: `string`):

Select the source country. United States covers 12 city and county portals; Australia covers NSW; New Zealand covers Far North; France covers the selected SDES datasets.

`maxResults` (type: `integer`):

Start with 10 records (about $0.05 plus the start event at 512 MB). For a larger export, raise this and your maximum cost per run: about $0.005 per record. This cap is shared across selected sources.

`dateFrom` (type: `string`):

Optional YYYY-MM-DD start date, inclusive. Leave blank for the 90 days before the end date. France and the US use the authorisation or issue date by default; NSW and Far North use the application date.

`dateTo` (type: `string`):

Optional YYYY-MM-DD end date, inclusive. Leave blank for today in UTC (US, NSW, Far North) or, for France, the coverage end of the latest monthly SDES file. France rows dated after that file's publication are not queried.

`zipCodes` (type: `array`):

Five-digit ZIP codes, for example 10001 or 78701. Max 20, OR between codes. Filtered by the city portal. Not available for Chicago, Orlando, New Orleans and Mesa, whose datasets have no ZIP code.

`departmentCodes` (type: `array`):

For example 69, 2A or 971. Max 20. AND with communeCodes if both are supplied.

`communeCodes` (type: `array`):

Exact codes, for example 69123 (Lyon). Max 20. Only for France.

`councils` (type: `array`):

For example Council of the City of Sydney or The Hills Shire Council. Max 5, OR between councils. Names are validated against the source's lookup.

`keywords` (type: `array`):

Case-insensitive words in the project description; OR between keywords. US portals filter them at the source (for example solar, roof, ADU, pool). In AU/NZ they are applied locally within date/area filters, so rare keywords can reach the request cap. Unsupported for France.

`sourceIds` (type: `array`):

Leave blank to use the country's default. US: us-nyc-dob, us-la-building, us-chicago-building, us-dallas-building, us-seattle-building, us-austin-building, us-orlando-building, us-new-orleans-building, us-cincinnati-building, us-mesa-building, us-baton-rouge-building, us-montgomery-md-residential, us-montgomery-md-commercial. France: fr-sdes-housing, fr-sdes-nonresidential, fr-sdes-development, fr-sdes-demolition. Australia: au-nsw-tracker. NZ: nz-fndc-building. Max 5, processed in order; maxResults is shared across them.

`dateField` (type: `string`):

Choose the event date used by the period filter. A submission, a decision and an issued authorisation are different events. Unsupported source/date combinations are rejected.

`maxRequests` (type: `integer`):

Leave empty: the Actor sizes requests from maxResults, including metadata and retries. A value here is a hard cap; reaching it ends the run successfully with a status message. Not a monetary spending cap.

Actor input object example

{
  "country": "US",
  "maxResults": 10,
  "dateField": "source_default"
}

Actor output Schema

`records` (type: `string`):

No description

`summary` (type: `string`):

No description

`coverage` (type: `string`):

No description

`safe_csv` (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

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 = {
    "country": "US",
    "maxResults": 10,
    "dateField": "source_default"
};

// Run the Actor and wait for it to finish
const run = await client.actor("gaelasao/planning-data-au-nz-fr").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

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 = {
    "country": "US",
    "maxResults": 10,
    "dateField": "source_default",
}

# Run the Actor and wait for it to finish
run = client.actor("gaelasao/planning-data-au-nz-fr").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

echo '{
  "country": "US",
  "maxResults": 10,
  "dateField": "source_default"
}' |
apify call gaelasao/planning-data-au-nz-fr --silent --output-dataset

MCP server setup

{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gaelasao/planning-data-au-nz-fr"
        }
    }
}

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/eDl4a1F6MH7fMyGjm/builds/fxhBagZ4n5Ya8oKCf/openapi.json

Building Permits API

เซิร์ฟเวอร์ MCP แบบโฮสต์

เอกสาร

Building Permits API: US Construction Leads, France, NSW, NZ (gaelasao/planning-data-au-nz-fr) Actor

Pricing

What's an Apify Actor?

How to integrate an Actor?

README

Ready-to-run examples

What can you do with building permit data?

Which building permits and planning applications are covered?

How to get your first results

Examples

United States: New York City permits in one ZIP code

United States: Dallas permits in two ZIP codes

United States: solar permits in Seattle and Austin

France: housing authorisations in Rhône

Australia: NSW applications in City of Sydney

New Zealand: Far North building applications

What does a result contain?

How do the filters work?

How much does the Building Permits API cost?

Frequently asked questions

Can I get permis de construire data for France?

Does it cover building permits in the United States?

Can I get contractor names and project values for US permits?

Does it cover all of Australia and New Zealand?

Can I get applicant companies, contacts or Far North street addresses?

Can I connect it to my own application?

How do I call it from a script?

Can I use it through an MCP connector?

Can I repeat the query or send the results to another tool?

Why did my run return fewer results than expected?

Are source text and statuses cleaned up?

Attribution and data rights

Support

Changelog

Actor input Schema

country (type: string):

maxResults (type: integer):

dateFrom (type: string):

dateTo (type: string):

zipCodes (type: array):

departmentCodes (type: array):

communeCodes (type: array):

councils (type: array):

keywords (type: array):

sourceIds (type: array):

dateField (type: string):

maxRequests (type: integer):

Actor input object example

Actor output Schema

records (type: string):

summary (type: string):

coverage (type: string):

safe_csv (type: string):

API

JavaScript example

Python example

CLI example

MCP server setup

OpenAPI specification

Building Permits API: US Construction Leads, France, NSW, NZ (`gaelasao/planning-data-au-nz-fr`) Actor

`country` (type: `string`):

`maxResults` (type: `integer`):

`dateFrom` (type: `string`):

`dateTo` (type: `string`):

`zipCodes` (type: `array`):

`departmentCodes` (type: `array`):

`communeCodes` (type: `array`):

`councils` (type: `array`):

`keywords` (type: `array`):

`sourceIds` (type: `array`):

`dateField` (type: `string`):

`maxRequests` (type: `integer`):

`records` (type: `string`):

`summary` (type: `string`):

`coverage` (type: `string`):

`safe_csv` (type: `string`):