2.1 API Key
A unique 32 character API key is used to authorise inbound requests to the APIs. To obtain an API key please visit
completed you will be emailed an API key along with links to documentation specifying how to call the APIs and the terms and conditions
associated with using the APIs.
Australia Post requires customers to use these APIs via HTTP GET over SSL (Secure Sockets Layer) protocol so as to protect the API keys.
The required design pattern is for customers to use AUTH-KEY and SSL for both the production and non-production websites. The API keys
cannot be used in address line calls and MUST be sent within the HTTP HEADERS.
2.1.1 Non-production API key
than live APIs.
The following API key is required to access these APIs:
28744ed5982391881611cca6cf5c2409
...
5.1 Postcode Search API
Search the collection of Postcode records for potential matches. The search criterion is location name or postcode with an optional state
filter. Request must be a HTTPS GET.
URL:
Formats:
xml, json (Default to xml if format not provided)
Requires Authorisation:
True (API Key)
Parameters:
1. [q]: Required. The search criterion used to drive the search query. This parameter will hold either the location name or postcode
2. [state]: Optional. Used to filter possible search results. Must be formatted using an Auspost accepted abbreviation (i.e. VIC
for Victoria, QLD for Queensland)
3. [excludePostBoxFlag]: Optional. Set value to true, if post boxes should be excluded from search results. That is
useful for PAC.
...
6.2 Service oriented API examples
These examples return results in XML format, however note that JSON format is also permitted.
Request type: HTTPS GET
Header: AUTH-KEY: {Use your personal 32 character API key}
Postcode search: