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.0.0 17 August 2026

First published release — The Trade API opens with light-vehicle glass: price it, check stock on it, and order it from your own software. Everything below is contractual from today — the reference is the whole agreement, not a summary of one.

What you can do

Resolve a vehicle to the glass we can supply for it — POST /fitment/glass. Send an InfoAgent IVDS report as-is, or an explicit make/model/year object if you are on another provider. We echo back the vehicle we matched.
Get your account's net price and our stock on hand, in one call — POST /availability.
Read our delivery days for your address — GET /delivery-schedule.
Place an order and read it back — POST /orders, GET /orders, GET /orders/{orderId}.
Look a part up by our number or by yours — GET /products/{sku}, which also reads Eurocode, NAGS AU, OEM and O'Brien's numbers as the path.
Pull the fitting materials for a part — GET /products/{sku}/fitting-materials.
Check we are up, without a key — GET /health.

How access works

One key, one trade account, in the X-Globe-Api-Key header on every request. The key decides your prices, your catalogue and your branch — there is no account parameter on any request.
Building for several trade accounts? One key per account, and your software sends the key of the account it is acting for. There is no master key.
Keys rotate, and we run two keys on your account during the window so you cut over without downtime.
A sandbox key is issued alongside your production key at onboarding. The sandbox runs the full contract against our live catalogue — real parts, your real prices, live stock — and accepts orders that are never fulfilled or billed.

What version 1 does not cover

Welshpool (WA) only. Every response is that branch's stock and that branch's delivery.
Light vehicles only.
Single-unit pricing. There is no quantity-break ladder.
No registration or VIN lookup. You resolve the vehicle with your own vehicle-data provider and send us the vehicle.
Each of these widens in a later major version, never silently.

Reading responses safely

A missing value reaches you three ways and they mean different things: the property is present carrying null (we looked, nothing on file), an empty list [] (we resolved your request and hold nothing), or absent entirely (the question does not apply here).
We never send a placeholder to mean unknown — no sentinel code, no empty string, no zero standing in for missing.
401 and 403 are terminal. Never retry them: the credential or its entitlement is wrong and stays wrong until someone changes it.
Every value set we return is closed and enumerated in full in the reference. A new member is a new major version — except problem.type, which is documented as open.

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.