Hooray, our new website is live!

We've revamped our space to be simpler and more welcoming for everyone. Why the change? Discover the reasons behind our redesign.

Get the Data

Planning application data is available programmatically. Details of the API are listed below.

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 JSON, GeoJSON and GeoRSS. The examples below return JSON. To get GeoJSON instead simply replace ".json" in the URL with ".geojson". For GeoRSS replace ".json" with ".rss".

To use the API you will to register for an account or sign in to your existing account. Once you've done that, return to this page and the you will be able to create an API key here.

API calls

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.


Area by longitude/latitude

Return applications within a rectangle defined by longitude/latitude.


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.



Return applications for a specific postcode area



Return applications in a suburb. Including “state” and “postcode” in the search is optional.


Extra query parameters

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


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.



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.


Warning about client side API queries

Client-side API queries are supported using CORS. You might do this, for example, in a Javascript application that runs in the browser making requests directly to the Planning Alerts API. This is fine for testing. However, this should not be used in production as you would be effectively making your API key public, which is a very bad. It is your responsibility to keep the API key safe and secure.

Instead we recommend either loading the data ahead of time server-side and passing the data to your client or alternatively proxying the client-side requests through your own server where you add the API key.


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.

Standard agreements for commercial use are at oaf.org.au/standard-agreements/planningalerts-commercial. 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.

Be Nice

The Planning Alerts service is intended to help people be aware of what's happening in their local neighborhood, and to enable a civil discussion about those changes.

Don't use the service (or information obtained from the service) to market goods or services to individuals.

Don't use the service (or information obtained from the service) to harass or intimidate a person.