How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Australia Post Endpoints API

The Endpoints API from Australia Post — 9 operation(s) for endpoints.

Australia Post Endpoints API is one of 4 APIs that Australia Post publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 9 operations across 9 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 1.3.0.

Requests are made against a single base URL, https://digitalapi.auspost.com.au/delivery-partner.

9 operations 9 paths 17 schemas 8 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.3.0
Base URL
https://digitalapi.auspost.com.au
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Australia Post Endpoints API declares 1 security scheme for authenticating requests. An API key is passed in the header as AUTH-KEY (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 8 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Endpoints 9
POST
/api/v1/event
Sends the delivery event to Australia Post
event body → 200
GET
/points/postcode/{postcode}
getPointsByPostcode
getGeoLocationsByPostCodeUsingGET 4 params → 200
GET
/points/workcentres/{work_centre_id}
getPointsByWorkCenterID
getGeoLocationsByWcidUsingGET 4 params → 200
GET
/points/deliverypoints/{delivery_point_id}
getPointsByDeliveryPointId
getGeoLocationsByDeliveryPointIdUsingGET 4 params → 200
GET
/points/{location_code}
getPointsByLocationCode
getPointsByLocationCodeUsingGET 3 params → 200
GET
/points/type/{points_type}
getPointsByType
getPointsByTypeUsingGET 3 params → 200
GET
/points/geo/{longitude}/{latitude}
getPointsByGeoCoordinates
getGeoLocationsUsingGET 8 params → 200
GET
/services
getServices
getServicesUsingGET 1 param → 200
GET
/services/{service_codes}
getServicesByServiceCodes
getServicesByServiceCodesUsingGET 2 params → 200

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are Point (17 properties), Address (12 properties), EventVO (9 properties), Hour (6 properties). Each schema is shown below with its type and property counts.

Location
object
This object describes the precise location of an Australia Post outlet or facility. This object always returns latitude and longitude values for a point, altho…
3 properties
AuditVO
object
Audit details.
2 properties 2 required
EventVO
object
An event originating in a partner's system, which AP is to be informed of.
9 properties 6 required
LocationVO
object
Location details
2 properties 2 required
AttachmentVO
object
Image attachments showing details of a delivery (e.g. for damaged article).
2 properties 2 required
Hour
object
An Hour object describes a range of date and time-related information for a specific Australia Post outlet or facility.
6 properties
PointsResponse
object
1 property
DeliveryVO
object
Delivery details.
2 properties
ProofOfDeliveryVO
object
The details of the delivery.
5 properties
ServiceActionsVO
object
Elements relating to the specific Product Service Codes, e.g. Service Codes 81, 82 and 83 are for alcohol and require ID to be presented in some Australian Sta…
4 properties
EventOriginatorVO
object
Details of the System where the event originated.
2 properties 2 required
Address
object
An Address object contains full street address information for a specific Australia Post outlet or facility.
12 properties
FacilityVO
object
Facility details
1 property
Point
object
A point object is a descriptive record of an individual Australia Post outlet or facility, that includes location, contact and service availability data.
17 properties
ArticleVO
object
Article details.
3 properties 1 required
SystemVO
object
The System where the event originated.
2 properties 2 required
PersonVO
object
The person associated with the origin of the event.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

australia-post-endpoints-api-openapi.yml Raw ↑

Other APIs Australia Post publishes across the network.

Australia Post Shipping and Tracking API
Australia Post Postage Assessment Calculator API
Australia Post Delivery Choices API
Where this information came from

This is an independent, third-party profile of Australia Post Endpoints API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.