Get the Data - API

Planning application data is available programmatically as feeds which can be used in most web mapping APIs and desktop GIS software like mapufacture and Yahoo Pipes. Details of the API are listed below.

Non-commercial, low-volume use of this service is free. Read more.

All the API calls listed below return planning application sorted by the date they were scraped from the planning authority website with the most recent listed first.

The API can return different formats including GeoRSS, JSON and JSONP. The examples below return JSON. To get GeoRSS instead simply replace ".js" in the URL with ".rss". To get JSONP add the query parameter "callback".

API documentation

Single Location by address

Return applications near a given street address. The area included is a circle with a radius of the given size (in metres) with the address at its center. Suggested sizes are 400, 800 or 4000 metres.

http://api.planningalerts.org.au/applications.js?address=[address]&radius=[distance_in_metres]

view example | view on a map

Single Location by longitude/latitude

Return applications near a given longitude/latitude. The area included is a circle with a radius of the given size (in metres) with the longitude/latitude at its center. Suggested sizes are 400, 800 or 4000 metres.

http://api.planningalerts.org.au/applications.js?lat=[latitude]&lng=[longitude]&radius=[distance_in_metres]

view example | view on a map

Area by longitude/latitude

Return applications within a rectangle defined by longitude/latitude.

http://api.planningalerts.org.au/applications.js?bottom_left_lat=[latitude]&bottom_left_lng=[longitude]&top_right_lat=[latitude]&top_right_lng=[longitude]

view example | view on a map

Planning authority

Return applications for a specific planning authority (e.g. a local council) by authority short name. To discover the authority short name to use here, find the planning authority on the list of authorities and follow the link. The url has the authority short name in it.

http://api.planningalerts.org.au/authorities/[name]/applications.js

view example | view on a map

Postcode

Return applications for a specific postcode area

http://api.planningalerts.org.au/applications.js?postcode=[postcode]

view example | view on a map

Suburb

Return applications in a suburb. Including "state" in the search is optional.

http://api.planningalerts.org.au/applications.js?state=[state]&suburb=[suburb]

view example | view on a map

Extra query parameters

There are several parameters that can be applied to each of the above queries for extra usefulness.

page

API calls return a maximum of 100 results. To retrieve more results simply do another request with page set to 2, 3, etc... Not setting the page parameter is the same as requesting page 1.

http://api.planningalerts.org.au/applications.js?page=2&postcode=2780
count

API calls by default return a maximum of 100 results. To return less than that per page simply set the count parameter to the maximum number you want to return.

http://api.planningalerts.org.au/applications.js?count=10&postcode=2780
style

For georss, by setting "style" to "html" it will return an html formatted description in the georss feed rather than the default plain text. This is especially useful when a georss feed is embedded in a map as in some of the examples above.

http://api.planningalerts.org.au/applications.rss?postcode=2780&style=html
callback

To return JSONP set "callback" to the name of your javascript callback function.

http://api.planningalerts.org.au/applications.js?callback=my_callback&postcode=2780

Usage & License

Data is licensed under the Creative Commons Attribution-Share Alike 3.0 license.

Low volume, non-commercial use of the API service is free. We ask that personal and non-profit use of this service attribute the OpenAustralia Foundation on your website or application.

Please contact us for commercial use. Commercial users may include Real Estate Agencies, Architects, Planners or Builders.

Also, please get in touch if you intend to use the service on a large scale. In order to maintain quality of service for our API users, this service is rate limited by default to approximately 1000 requests per day.

We offer a range of paid options, from rate-limited to unlimited use of this service.