Free sandbox: try any request below on the sample suburbs, no signup. For every suburb, create an API key.

Microburbs Property Data API

Suburb - Environment

Aircraft noise zones (by suburb)

GET/v1/suburbs/{suburb_name}/mesh-blocks/aircraft-noise20¢ per call

How much of a suburb or city block sits inside the published aircraft-noise zones around Australian airports: share of addresses in each noise band, the loudest band, and whether the airport has a night curfew.

Coverage: About 250 suburbs and 4,700 blocks have at least one address inside a published zone (NSW, VIC, QLD, SA, WA, NT); about 1,700 more suburbs and 110,000 blocks within 20 km of such an airport are listed at 0%. Everywhere else, and Brisbane, Hobart and Canberra, is not listed. Current to 2026-10-19. Full description, field list and method: /v1/datasets/aircraft-noise.

One call returns every mesh block in the suburb.

Exact suburb identifier required. Exact official suburb name (SAL), e.g. Burwood (NSW) — many suburbs carry a state suffix. If starting from free text or an unverified bare name, first call GET /v1/geocode/suburb?q=<text>, then use the exact data[].area_name it returns. Suburb data endpoints do not guess a state or typo-correct names.

Authorization

Bearer tokentest

Sandbox key test works for the allowlisted GNAF + SAL — no signup.

Request

The only values you send. Fields under Responses below are what comes back — you never pass those.

Path parameters

suburb_namestringrequired

Exact official suburb name (SAL), e.g. `Burwood (NSW)` — many suburbs carry a state suffix. If starting from free text or an unverified bare name, first call `GET /v1/geocode/suburb?q=<text>`, then use the exact `data[].area_name` it returns. Suburb data endpoints do not guess a state or typo-correct names.

Query parameters

None — this endpoint accepts no query parameters. Call the path above with your bearer token and nothing else.

Responses

Successful Response

application/json

DatasetBlocksfields returned to you

datasetstringalways returned

Dataset slug.

suburbstringalways returned

Canonical suburb name.

as_ofstring · datealways returned

Date the dataset is current to.

modelledbooleanalways returned

True when the figures are modelled estimates.

blocksintegeralways returned

Number of mesh blocks with data.

rowsarray of DatasetBlockRowalways returned

One row per block, field and period.

GET/v1/suburbs/{suburb_name}/mesh-blocks/aircraft-noise

cURL

curl --request GET \
  --url 'https://api.microburbs.com.au/v1/suburbs/Belmont%20North/mesh-blocks/aircraft-noise' \
  --header 'Authorization: Bearer test'

Example Responses

Show schema

{
  "data": {
    "dataset": "aircraft-noise",
    "suburb": "Bondi",
    "as_of": "2026-10-19",
    "modelled": false,
    "blocks": 142,
    "rows": [
      {
        "mb_code": "10825880000",
        "field": "addresses_total",
        "period": "2026-10-19",
        "value": 46
      },
      {
        "mb_code": "10825880000",
        "field": "addresses_in_zone",
        "period": "2026-10-19",
        "value": 0
      },
      {
        "mb_code": "10825880000",
        "field": "in_zone_share_pct",
        "period": "2026-10-19",
        "value": 0
      }
    ]
  }
}

Successful Response200

application/json

About this dataset

About 250 suburbs and 4,700 blocks have at least one address inside a published zone (NSW, VIC, QLD, SA, WA, NT); about 1,700 more suburbs and 110,000 blocks within 20 km of such an airport are listed at 0%. Everywhere else, and Brisbane, Hobart and Canberra, is not listed. Current to 2026-10-19; refreshed yearly.

What it is

For every suburb and mesh block (a city block of roughly 30 to 60 homes) that has at least one address inside an official airport noise zone, the share of its addresses in each noise-exposure band, the loudest band present, and whether the serving airport has a night curfew. About 250 suburbs and 4,700 blocks are listed, around 25 airports and airfields (Sydney, Melbourne, Adelaide, Perth, Gold Coast, Sunshine Coast, Western Sydney, Townsville, Darwin and a number of defence airfields). Areas within about 20 km of an airport whose zone we hold, but with no address inside it, are listed with 0% so that 'outside the zone' can be told apart from 'no data'.

What it shows

Address counts (total, inside a zone); the share of all addresses inside any zone; the share whose highest zone is 15-20, 20-25, 25-30 or 30-and-above on the Australian noise exposure forecast scale; the loudest band present (15, 20, 25 or 30); the share of zone addresses under an airport with a night curfew; and how much of the zone comes from an approximate contour (Sydney only).

Why use it

Planning rules, insurance, building insulation requirements and buyer sentiment all key off these zones, and a zone is the only official statement of aircraft exposure. Block detail separates the streets under the approach from the streets two blocks away, which a suburb average hides. Use it to flag homes for disclosure, to screen a shortlist, to add a noise line to a property report, or to explain a price difference between look-alike streets.

How it is built

We overlay each airport's published noise-zone contours on our address points; an address in several zones takes its highest band, and counts are then rolled up to suburb and 2021 mesh block. Bands are the lower bound of the published exposure band (Melbourne's 20/25/30 contours are mapped to the same bands). Important limits: (1) a zone is a planning boundary for long-run average exposure, not a measure of what a resident hears; planes are heard well outside every zone, so a 0% means 'outside the published zone', never 'quiet', and an area absent from this dataset means we hold no zone for it; (2) we hold no usable zone for Brisbane Airport, Hobart or Canberra, so those cities are not represented; (3) Sydney Airport's zone is traced from the published 2039 forecast map and is approximate, flagged in approx_zone_share_pct; (4) about 9% of zone addresses could not be tied to a current address point and are not counted, so shares can be slightly low. For how often planes actually pass over a suburb, see the flight-paths dataset.

Fields

Field	Unit	Description
`addresses_total` Addresses in area	count	Number of addresses in the suburb or block (all address points, residential and other).
`addresses_in_zone` Addresses inside a noise zone	count	Addresses inside a published aircraft-noise zone (noise exposure of 15 or more).
`in_zone_share_pct` Share of addresses inside a noise zone	%	Addresses inside any published aircraft-noise zone as a percentage of all addresses in the area. Areas with no address inside a zone are not listed: that is 'no published zone', not 'quiet'.
`band_15_20_pct` Share in the 15-20 band	%	Share of all addresses whose highest zone is the 15-20 noise-exposure band (light; only some airfields publish this band).
`band_20_25_pct` Share in the 20-25 band	%	Share of all addresses whose highest zone is the 20-25 band (planes are noticeable; the usual lower limit of 'affected').
`band_25_30_pct` Share in the 25-30 band	%	Share of all addresses whose highest zone is the 25-30 band (frequent, clearly audible).
`band_30_plus_pct` Share in the 30+ bands	%	Share of all addresses whose highest zone is 30 or above (very high; new housing is usually restricted).
`highest_anef_band` Highest band present	band	Lower bound of the loudest published zone any address in the area sits in: 15, 20, 25 or 30 (30 means 30 and above).
`curfew_airport_share_pct` Zone addresses under an airport with a night curfew	%	Among in-zone addresses whose airport's curfew status is known, the share served by an airport with a night-time flight curfew. Absent where the status is unknown (most military airfields).
`approx_zone_share_pct` Share of zone taken from an approximate contour	%	Share of the area's in-zone addresses whose zone comes from the Sydney Airport 2039 forecast, which we trace from a published map and treat as approximate (band edges can be off by a block or two). 0 everywhere else.