Integrate IATA ONE Record logistics object API to track a baggage piece through its journey

Verified steps

1. Discover the ONE Record server endpoint for the baggage carrier; ONE Record uses a linked-data model where each server is self-hosted by the stakeholder (airline, handler) — obtain the base URL from the carrier's ONE Record endpoint registry.
2. Authenticate via OAuth 2.0 or the security mechanism required by the server (ONE Record 2.2.0 defers specific auth to the implementation); include the Bearer token in the Authorization header.
3. Create or retrieve the Piece logistics object via POST /logistics-objects (if you are the data owner) or GET /logistics-objects/{logisticsObjectId} if the airline owns the piece record — the ID is a URI.
4. Subscribe to change notifications for the Piece object: POST /notifications with a subscription payload specifying the logistics object URI and your callback endpoint; the server will POST change events to your callback as the baggage progresses.
5. On receiving a notification, fetch the updated Piece object; inspect the LogisticsEvents array for milestone events such as BKD (booked), RCS (received from shipper), DEP (departed), ARR (arrived), DLV (delivered to passenger), or TRM (transferred to another carrier).
6. Map ONE Record milestone codes to human-readable baggage status messages for passenger-facing display; handle missing or delayed events by falling back to the flight status board for the relevant segment.