id you want to store.
Usage is metered in credits. See the Credits guide for response headers and
usage behaviour.
When to use it
- Auto-fill suburb, state, postcode, coordinates, and boundary fields after address selection.
- Store structured address components instead of parsing
addressLabel. - Attach LGA, ward, SA1, mesh block, or ABS Statistical Area fields to a record.
- Inspect alternate address labels, secondary/unit records, and additional geocodes when present.
- Resolve an address ID you previously stored.
Request
Examples
Response
The exact values depend on the selected address and current data release. Enrich adds optional fields when that source metadata exists for the record. Coverage varies by address and geography, so treat every enrich-only field defensively.Enrich-only fields
Shared full-address fields
Boundary and enrich-only fields are optional. Handle missing nested objects defensively.
Integration tips
- Store the
idfrom Autocomplete or Validate instead of attempting to recreate it from address text. - Use Enrich only when you need the richest record; Autocomplete and Validate already return display and match-quality fields.
- Prefer
componentsover parsingaddressLabel. - Use
allGeocodesonly when your workflow needs to compare multiple geocode candidates. - Treat boundary data as source metadata that may change across official data releases.