Overview
This page explains every public field returned by the Prontiq Address API. It is written for developers implementing the API, analysts interpreting address and boundary data, and stakeholders who need to understand what each field means in plain English.packages/docs/openapi.json. It does not document private account APIs or
internal search, billing, or storage fields.How to read this page
Each field entry starts with a plain-English description, then moves into type, nullability, source classification, and gotchas. Source classification uses four labels:Quick reference
How G-NAF powers the API
G-NAF means Geocoded National Address File. It is Australia’s national address dataset, maintained by Geoscape and built from address information supplied by state, territory, and Commonwealth contributors. Prontiq uses G-NAF as the address corpus behind autocomplete, validation, enrichment, reverse geocoding, and locality lookup. Prontiq adds a public API layer on top of that source data: authenticated endpoints, match-quality scoring, simplified response shapes, debug diagnostics, and generated SDKs. Prontiq match fields describe how well a returned address matched the submitted request. G-NAF fields describe the address record itself.id changing.Autocomplete
Validate
Enrich
id into the full public address document.Reverse geocode
distance_m.Postcode lookup
Suburb lookup
Field reference
Address identity
Address identity
id as an opaque string. Do not parse state, locality, or record
meaning out of it. Pass it to Enrich when you
need the full address document after a user selects a suggestion.PRIMARY generally means a parent or building-level address.
SECONDARY generally means a child, unit, or subaddress record.Locality and postal fields
Locality and postal fields
NSW, VIC, QLD, SA, WA, TAS,
NT, and ACT. Query filters are case-insensitive, but responses
normalize state codes to uppercase.0,
and integer coercion loses leading zeroes.Prontiq match quality
Prontiq match quality
0 to 100. Use it for thresholds,
ranking, and analytics. It is not G-NAF record quality, deliverability, or
geocode precision.prontiqMatchScore.G-NAF record quality
G-NAF record quality
confidence describes how many upstream contributor datasets support the
address record. It does not describe how well the user’s submitted text
matched the record.confidence. Validate uses
top-level prontiqMatchScore and prontiqMatchQuality for request match
quality, while match.confidence remains source-record metadata.Geocode and location
Geocode and location
0 to 6. Treat the
value as source precision metadata and link to Geoscape’s official
documentation when your workflow needs the full reliability-code model.location when your integration wants a simple { lat, lon } shape.
Use geocode when you also need source precision and geocoding method
metadata.Administrative and statistical boundaries
Administrative and statistical boundaries
Enrich-only fields
Enrich-only fields
addressLabel.components.addressSiteName,
components.buildingName, components.flatType,
components.flatNumber, components.levelType,
components.levelNumber, components.lotNumber,
components.streetNumberFirst, components.streetNumberLast,
components.streetName, components.streetType, and
components.streetSuffix.allGeocodes[].latitude,
allGeocodes[].longitude, optional allGeocodes[].type, and optional
allGeocodes[].reliability.locality.id, locality.classification,
locality.neighbours, and locality.aliases.street.id, street.classification, and
street.aliases.aliases[].id, aliases[].addressLabel, and
aliases[].type.secondaries[].id and
secondaries[].addressLabel.Endpoint envelopes and aggregates
Endpoint envelopes and aggregates
total equals the number of suggestions returned, not an exhaustive
count of every possible match.match is null when the submitted address cannot be resolved to a
usable record. Even when match is present, use prontiqMatchScore and
prontiqMatchQuality to decide whether the match is strong enough for
your workflow.distance_m. Reverse geocode
also includes total, which reports how many records were found inside
the requested radius.distance_m appears only on Reverse geocode results. It is a proximity
measure, not match quality.address_count appears in postcode and suburb lookup responses. It is
dataset cardinality, not credits, quota, billing usage, or rate limiting.name, optional state, and address_count.postcode: preserving
leading zeroes is part of the public contract.bounds.top_left and bounds.bottom_right use snake_case field names for
v1 wire compatibility.total is the number of
suggestions returned in that response. In Reverse geocode, total is the
number of address records found inside the requested radius.Debug and errors
Debug and errors
debug=true is supplied.debug object.exact, prefix, fuzzy, and none.prontiqMatchScore, such as an explicit postcode or state mismatch.debug=true. Do not store it, sort by
it, or use it for business decisions.error.code, display or log error.message, and include
error.request_id when contacting support.error.code for branching. Do not parse error.message.error.code. Treat it as optional context rather
than a required schema for every error.Fields not present in default responses
Alias, canonical values, and storage
Prontiq returns canonical address values from the public contract. Users may type aliases, partial street names, or mixed-case locality names, but integrations should store the returnedid and display the returned address fields rather
than attempting to preserve the submitted text as the canonical record.
Store id, postcode, and boundary codes as strings. Treat optional nested
objects defensively: geocode, location, boundaries, and individual
boundary fields can be absent or null depending on source coverage.
Freshness and lifecycle
Address source data and boundary data change across official releases. A storedid is the right key to keep, but the document behind that key can gain, lose,
or update metadata over time. If your product relies on current boundaries,
geocodes, or source metadata, re-enrich stored IDs on a regular release cadence.
An ID that no longer resolves returns a NOT_FOUND error from
Enrich. Handle that as stale source data rather than
as a user input error.
Semantic origin table
The repo verifies the public field names, types, examples, and source classifications below. It does not encode exact upstream G-NAF table and column lineage for every field, so this page does not invent table-column precision that cannot be checked from source.Implementation checklist
Store stable identifiers as strings
id, postcode, Mesh Block codes, ABS area codes, and electorate
codes as strings. Enrich-only values such as legalParcelId,
sourceDataRelease, boundaries.sa1, aliases, and secondary IDs should
also be stored as strings when your workflow needs them.Use Prontiq fields for match decisions
prontiqMatchScore and prontiqMatchQuality for accept, confirm, or
reject workflows.Treat G-NAF confidence as provenance
confidence tells you about source-record support. It is not request match
quality.Remember reliability is inverted
geocode.reliability values indicate more precise geocodes.Keep debug out of product logic
debug.searchScore is optional, unstable, and diagnostic only.Preserve v1 snake_case fields
distance_m, address_count, top_left, bottom_right, and
error.request_id exactly as documented.Treat optional nested objects defensively
geocode, location, boundaries, and individual boundary fields can be
absent or null.Use Enrich after selection
id when your application needs coordinates and boundary data.Re-enrich stored IDs periodically
id remains stable.Handle stale IDs explicitly
NOT_FOUND response from Enrich means the stored id no longer resolves
in the current public corpus.