DCSA Reference Documentation / Standards / Standard Releases / Commercial Schedules / Archive / Commercial Schedules v1.0.2
DCSA CS 1.0.2 - Changelog
Archived release: Commercial Schedules v1.0.2 has been superseded. View the current v1 documentation.
Contents
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.