MSC adopts DCSA API for standardised schedule data exchange

0
24

MSC has confirmed its adoption of the Digital Container Shipping Association (DCSA) Commercial Schedules API, providing customers and partners with real-time access to standardised vessel schedule data through direct system integration.

The implementation will allow for improved transparency and automation across container logistics operations by enabling near real-time data exchange between MSC and its stakeholders, removing the need for manual updates and reducing reliance on multiple integration formats.

The DCSA Commercial Schedules API offers access to data including point-to-point routings, vessel schedules, and port schedules. These standardised data sets are designed to simplify cross-carrier integration for shippers, freight forwarders, and digital platforms.

MSC says it has fully adopted the point-to-point endpoint of the API, with development underway for the vessel schedule and port schedule endpoints. The company also plans to roll out additional DCSA-standard APIs for bookings and bills of lading.

“The adoption of DCSA standards is an important step in making the shipping industry more digital. By fostering collaboration between carriers, ports, and logistics providers, data sharing becomes a smoother process, resulting in enhanced real-time, cross-carrier visibility,” said MSC in a statement.

“The use of standardised APIs gives beneficial cargo owners and freight forwarders more accurate, actionable information which enhances operational efficiency on a wider scale.”

“At MSC, our Digital Solutions follow the standards to improve compatibility, growth, and cost savings for our customers. Ultimately, this enhances customer satisfaction by enabling improved planning and reduction in manual intervention, helping improve overall supply chain resilience and profitability.”

MSC has also launched a Developer Portal to support integration with its API services, offering documentation and guidelines for developers to connect to its system using both API and EDI formats.