Download the DCSA Track and Trace v2.2 OpenAPI specification from the DCSA GitHub repository at github.com/dcsaorg/DCSA-OpenAPI; review the Event Structure Definitions and DCSA Industry Blueprint 3.0.
Identify the three primary event categories: Transport Events (vessel departure/arrival), Equipment Events (gate-in/out, load/discharge), and Shipment Events (booking confirmed, B/L issued).
For each carrier integration, obtain API credentials from the carrier developer portal (Maersk, Hapag-Lloyd, etc.) and confirm which DCSA T&T version they implement; map any carrier-specific event codes to DCSA equivalents.
Build a normalised event ingestion layer that maps carrier API responses to the DCSA event schema; store eventType, eventDateTime, eventClassifierCode, and location fields in a canonical format.
Implement the DCSA Subscription Callback API v1.0 on your server to receive push notifications from carriers that support server-to-server push; fall back to polling for carriers that do not.
Validate your implementation against the DCSA conformance test suite available on GitHub before going live with each carrier integration.
Known gotchas
Carrier adoption of DCSA standards is uneven; as of 2026 most major carriers support T&T v2.x, but event completeness and latency vary significantly — do not assume a milestone will fire at every carrier.
DCSA event timestamps use UTC ISO 8601 format with timezone offset; some carrier implementations omit the offset or use local port time, which will corrupt ETA calculations if not normalised.
The DCSA eBL 3.0 and T&T standards are separate specifications; implementing T&T does not give you eBL transfer capabilities — those require the separate PINT API integration.
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