The Digital Container Shipping Association (DCSA) has released version 2.2 of its Track & Trace Interface Standard for customer-facing events.
The updated version includes the DCSA Subscription Callback API, which allows customers (shippers/consignees) to subscribe to receive automatic updates of shipment events from carriers.
Security has been enhanced with subscription-ID and notification-signature headers. The release also supports a better customer experience with more efficient data inquiry and handling, including support for the following document events: Cargo Survey, Customs Inspection, Verified Gross Mass, Dangerous Goods Declaration, and Out of Gauge Declaration.
API definitions and reference implementation have also been updated.
API definitions can be downloaded from SwaggerHub and the new reference implementation is available on GitHub.
All accompanying documents: DCSA Industry Blueprint 3.0, Information Model 3.3, Information Model 3.3- Reading Guide, Event Structure Definitions 2.2, Event naming convention 2.2, Track & Trace Interface Standard 2.2, Track & Trace Interface Standard 2.2 – Reading Guide, DCSA API Design Principles 1.1, DCSA Subscription Callback API 1.0, and web glossary of terms, can be downloaded here.
Earlier this month the MSC Mediterranean Shipping Company (MSC) became the first major carrier to fully adopt BIC Facility Codes (BFC) for all depots globally.
All of MSC’s depots are now identifiable with a 9-character BFC, moving one step further on the digitalisation journey.
The BIC Facility Codes were created through a major harmonisation project conducted in November 2020 by the Bureau International des Containers (BIC) with the assistance of the Digital Container Shipping Association (DCSA).