DCSA Reference Documentation / Standards / Standard Releases / Arrival Notice / Arrival Notice v1.0.1
DCSA Arrival Notice 1.0.1 - Implementing Arrival Notice Standard
This is a guide to implementing the DCSA Arrival Notice (AN) standard version 1.0, written for the technical teams of DCSA adopting organizations.
Contents
Reference Documentation
To get acquainted with the standard, refer to the Arrival Notice Introduction.
To understand the Purpose & Scope, User Stories, Use Cases, Endpoint Overview, Business Process Model and Data Overview of the standard, refer to the Arrival Notice Documentation page.
To understand the data structures used by the standard and how they can be mapped to your own organization’s data types, consult the Information Model.
Implementing the Standard
The DCSA Arrival Notice 1.0 standard is designed and is expected to be implemented following the DCSA API Design and Implementation Guidelines 2025.Q4 (formerly named v3.0).
To review the reference implementation of the Arrival Notice standard, created by DCSA to verify the standard and used for measuring the conformance of adopter implementations, consult the Arrival Notice module of the DCSA conformance GitHub repository.
To ensure that your organization becomes a successful adopter in the DCSA Arrival Notice standard API ecosystem, use the DCSA conformance framework periodically throughout your implementation project, to measure the conformance of your implementation and to improve it as needed.
You can use a DCSA conformance sandbox as a counterpart in your development, since it allows you to easily test the most relevant conformance scenarios that your application needs to support. The Arrival Notice standard includes the list of conformance scenarios and validations that adopters are expected to support.
The DCSA Arrival Notice OpenAPI specification is available publicly on SwaggerHub.
Publisher Implementation
To implement the Arrival Notice standard API as a publisher, use your organization’s technology stack to implement the “GET /arrival-notices” endpoint of the Arrival Notice OpenAPI specification.
Subscriber Implementation
To receive Arrival Notices from any publisher, use your organization’s technology stack to build the “POST /arrival-notices” endpoint of the Arrival Notice OpenAPI specification.
To optionally receive Arrival Notice notifications from any publisher, use your organization’s technology stack to implement the “POST /arrival-notice-notifications” endpoint of the Arrival Notice OpenAPI specification.
Use the publisher’s proprietary process to register your endpoint(s) for receiving arrival notices and/or notifications.
Versions overview
List of changes and the version they are released in
| Version | Date of Publication | Change | Purpose of change |
|---|---|---|---|
| 1.0.1 | 2026-03-13 | Added a new optional object “Place of BL Issue”. | The Place of BL Issue is important for the release of the cargo since the shipper may have an agreement with the carrier/consignee to issue the BL at destination. In that case, the BL must be printed at destination. This is used as a workaround when Seaway bills cannot be used. |
| 1.0.1 | 2026-03-13 | Added Seals type, placement and additional sources:CNS (Consolidator)CST (Customer)TER (Terminal) | Support additional seals information. |
| 1.0.1 | 2026-03-13 | Added a new optional field facilityName in the Facility object. | Allow parties to specify facilities which are not identified by an SMDG / BIC code. |
| 1.0.1 | 2026-03-13 | 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. |
| 1.0.0 | 2025-11-27 | Initial release of Arrival Notice. | N/A |