Trade API changelog

How we version

We add without warning and we never break without a new major version. New endpoints, new optional request fields and new response properties can arrive at any time — ignore any response property you do not recognise rather than failing on it. Anything else is a breaking change, and a breaking change ships at a new base path, so your integration keeps running against the old one until you choose to move.

The rules that bind us are in the Compatibility section of the API reference.

v1.10.0 18 August 2026

First published release — Light-vehicle glass, priced and ordered from your own software. Nine endpoints; the API reference is the whole of what they do.

Added

POST /fitment/glass — a vehicle in, every glass part we carry for it out
POST /availability — your net price and our stock on hand, in one call
GET /delivery-schedule — our delivery days for your address
POST /orders — place an order
GET /orders — list your orders
GET /orders/{orderId} — read one order back
GET /products/{sku} — a part by our number, or by Eurocode, NAGS AU, OEM or O'Brien's
GET /products/{sku}/fitting-materials — the fitting materials for a part
GET /health — are we up, no key needed

Questions, or a limit you need raised — dev@globeparts.com.au (Globe Parts — Integrations).
The contract: the API reference. The machine-readable document: /spec.yaml.