DCSA Reference Documentation / Standards / Standard Releases / Commercial Schedules / Commercial Schedules v1

DCSA CS 1.0.3 - Changelog

Contents

Version 1.0.3 - 2026-06-12

Vessel Schedules: Add optional responseScope query parameter to control whether full voyages or only matched transport calls are returned. This change enables API consumers to control whether the Vessel Schedules endpoint returns the full matched voyage or only the transport calls matching the query parameters. The optional parameter, responseScope, supports FULL_VOYAGE and MATCHED_CALLS. If omitted, the value must be interpreted as FULL_VOYAGE to preserve backward compatibility.

Point-to-Point routings: Add co2e to solution and leg footprint objects. This change adds support for CO₂ equivalent emissions by introducing a co2e property in the footprint objects at solution and leg level. It allows carriers to provide CO₂e values in addition to existing CO₂ values where available. The reported values represent total estimated emissions for the routing solution and/or individual legs, typically per TEU, not emissions intensity values such as per TEU-km.

Point-to-Point routings: Add cargoType query filter. This change enables API consumers to request point-to-point routing solutions for a specific cargo type, initially DRY or REEFER. The cargo type may influence which routing solutions are returned, which transport legs are feasible, and which footprint values are reported.

Point-to-Point routings: Add an intermediateCalls object within a Leg to group non-transhipment intermediate transport calls. This change enables grouping of intermediate non-transhipment transport calls within a leg, avoiding the need to represent each call as a separate leg. It addresses usability challenges faced by solution providers when consuming richer schedule data, allowing simplified UI presentation while preserving full operational detail and ensuring consistent comparability across carriers.

Version 1.0.2 - 2026-02-13

Point-to-Point routings: Add transportCallReference to departure. Add transportCallReference to arrival. This will help consumers better identify arrivals and departures in the provided legs.

Point-to-Point routings: Add an object to support sharing the emissions footprint per leg and solution. This helps consumers assess routing options when footprint is a criterion for their choice.

Point-to-Point routings: Add a cut-offs object in the legs to support sharing leg-specific cut-offs. This helps carriers share cut-off information for legs that are not the first maritime leg with consumers, when available.

Update the description of the timestamp to align with other standards. Align with current standards, API design principles, and guidelines.

Add a new optional field facilityName in Location objects. Allow parties to specify facilities which are not identified by an SMDG / BIC code.

Added a new optional field addressLines in the Address object. Allow to capture unstructured address lines, used as a fallback when structured address fields are unavailable.

Don’t refer to the DCSA errorCode page, the API implementor maintains the codes returned. Fix bug.

Remove empty parameters on the endPoint root level. Fix bug.

Next-Page-Cursor, as defined, is impossible to comply with and is considered a bug to fix. Going forward, any filter parameters must be provided alongside the cursor parameter (this aligns with how it is done in AN (Arrival Notice)). Fix bug.

Version 1.0.1 - 2025-04-25

Added a new optional property routingReference (Routing reference) in the point-to-point API response endpoint. This will allow customers who integrate with the DCSA Booking API and Commercial Schedules API (point-to-point) to place a booking request with a specific routing previously fetched from Commercial Schedules, so that the booking will be created with the exact routing they need, without spending extra time re-keying information (such as vessel and service name) or on booking amendments due to routing discrepancies.

Version 1.0.0 - 2024-09-23

N/A.