Generate a DCSA-compliant Track and Trace v2.2 TransportEvent payload and implement the event subscription webhook for multi-carrier ocean tracking
domain: dcsa.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the DCSA T&T v2.2 OpenAPI specification to understand the TransportEvent, EquipmentEvent, and ShipmentEvent object schemas and the required eventClassifierCode values
Implement the GET /v2/events endpoint with filter parameters (transportDocumentReference, equipmentReference) to pull current event history for a shipment
Register a webhook subscription via POST /v2/event-subscriptions with your callback URL and the event type filters you want to receive
Validate inbound webhook payloads against the DCSA event schema, mapping DCSA event type codes to your internal milestone taxonomy
Handle the DCSA pagination model (cursor-based) when pulling historical events for a backlog of containers on initial integration
Known gotchas
Not all carrier implementations of DCSA T&T are at the same version; verify the carrier's conformance level before assuming full v2.2 field coverage
The DCSA eventCreatedDateTime is when the carrier system recorded the event, not when the physical milestone occurred; use eventDateTime for the physical occurrence
DCSA requires HTTPS webhook endpoints with TLS 1.2 or higher and recommends HMAC signature verification; implement signature validation before trusting payload content
Give your agent this knowledge — and 15,800+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?