Authenticate with the ONE Record server hosting the air freight operator's data using OAuth 2.0 bearer token; obtain the LogisticsObject URI for the Shipment object associated with the air waybill number
Request the Waybill LogisticsObject via GET {server}/logistics-objects/{waybill-id} with Accept: application/ld+json; inspect the waybillPrefix, waybillNumber, and arrivalLocation fields
Traverse the shipment containment graph by following the goodsItems links to reach individual Piece LogisticsObjects; each Piece has a physicalDimensions, specialHandlingCodes, and events array
Subscribe to LogisticsObject change events via POST /subscriptions on the ONE Record server: specify the subscribedTo URI as the Waybill LogisticsObject URI and the eventType as CREATE to receive new LogisticsEvent additions
Receive inbound webhook notifications containing a LogisticsEvent payload; extract the eventTimeStamp, eventCode (using IATA CXML event code vocabulary e.g. DEP for departed, ARR for arrived, RCS for received), and location
Map IATA event codes to your canonical air freight tracking states; persist each event with the Piece or Shipment URI as the correlation key for multi-piece AWB tracking
Known gotchas
IATA ONE Record is still in active adoption; not all carriers expose a ONE Record server with real-time event data; many continue to use IATA Cargo-XML FSU (Freight Status Update) messages for actual event exchange while offering ONE Record as a read-only view
ONE Record LogisticsObject URIs are not standardized in format across implementations; a URI from carrier A's server cannot be used to query carrier B's server for a connecting flight segment; you must follow the server-specific URI scheme from each operator
ONE Record subscription webhooks require your receiver endpoint to be TLS 1.2+ with a publicly trusted certificate; self-signed certificates are rejected by compliant ONE Record server implementations
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp