Track a booking

Endpoint

GET /api/bookings/v4/track/{id}

Returns tracking information for a confirmed booking. {id} may be a booking ID or, for some couriers, a connote / tracking reference.

There is also an unversioned alias: GET /api/bookings/track/{id}.

Authentication

Path parameters

Parameter	Type	Required	Description
`id`	integer or string	Yes	Booking ID, or a courier connote / tracking reference where supported.

Example request

curl -X GET \
  -H "Api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  https://www.transdirect.com.au/api/bookings/v4/track/12345678

Response shape

Tracking is aggregated per connote / item label. On success the JSON body is an object keyed by connote (or item label), each value an array of event rows. Field names are consistent, but availability of each field varies by courier.

{
  "ALD123456789": [
    {
      "date": "2025-08-18 15:30:00",
      "status": "Picked up",
      "description": "Shipment collected from sender",
      "location": "Sydney",
      "pod_url": null,
      "delivery_date": null,
      "track_status": "1"
    },
    {
      "date": "2025-08-19 06:00:00",
      "status": "In transit",
      "description": "Arrived at Melbourne depot",
      "location": "Melbourne",
      "pod_url": null,
      "delivery_date": null,
      "track_status": "2"
    }
  ]
}

When a proof-of-delivery URL is available it may also appear as a top-level pod_url on the response for some couriers.

Event fields

Field	Type	Description
`date`	string \| null	Event timestamp as reported by the courier.
`status`	string \| null	Courier status label for the event.
`description`	string \| null	Human-readable description of the event.
`location`	string \| null	Depot or location associated with the event.
`pod_url`	string \| null	Proof-of-delivery document URL when available.
`delivery_date`	string \| null	Delivery date when the shipment is delivered.
`track_status`	string \| number \| null	Normalised tracking stage when the courier provides one (see below).

Normalised `track_status` values

When present, numeric stage codes mean:

Status code	Meaning
`0`	Not available — not yet scanned
`1`	Picked up
`2`	In transit
`3`	Out for delivery
`4`	Delivered
`-1`	Futile / failed delivery attempt
`-2`	Check address
`-3`	Damaged

Not every courier populates track_status on every event — always prefer description / status for display when the code is missing.

Error responses

Status code	Description
`400`	No booking matched the id/reference, or tracking is not yet available. Body often includes `error` and/or a default message.
`401`	Unauthorised — invalid or missing credentials (authenticated path).