Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 24 additions & 2 deletions ebl/v3/issuance/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,30 @@ The DCSA Bill of Lading Issuance API is specified on [**SwaggerHub**](https://ap
Publications related to the Bill of Lading Issuance API:
- [Glossary of Terms](https://knowledge.dcsa.org/s/glossary) maintained on the [dcsa.org](https://dcsa.org) website
- [Bill of Lading](https://dcsa.org/standards/ebill-of-lading/) maintained on the [dcsa.org](https://dcsa.org) website (contains documents and publications)
- [Bill of Lading](./../) maintained here on GitHub
- [Bill of Lading Issuance Response](./../issuance_response/) maintained here on GitHub (the Issuance Response API linked to this API)
- [Bill of Lading](./..) maintained here on GitHub

<a name="v303"></a>[Release v3.0.3 (TBD 2026)](https://app.swaggerhub.com/apis-docs/dcsaorg/DCSA_EBL_ISS/3.0.3)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Placeholder release date 🐞 Bug ⚙ Maintainability

The new v3.0.3 release entry uses a placeholder date "TBD 2026", unlike other releases which have a
concrete date. If merged, this leaves the changelog in an incomplete/outdated state.
Agent Prompt
### Issue description
The v3.0.3 release note header contains a placeholder date ("TBD 2026"), which will ship as incomplete documentation.

### Issue Context
Other releases in the same file use a concrete date format, e.g. "(14 November 2025)".

### Fix Focus Areas
- ebl/v3/issuance/README.md[10-10]

### Suggested change
Replace the placeholder with the actual v3.0.3 release date using the same style as other entries (or remove the date entirely until it is known, but avoid leaving "TBD" in `master`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---
This is a patch version for the DCSA Issuance API. eBL Solution Providers updated:
- examples on endpoints have been added
- `errorCode` description updated
- removed `TODO` comments
- `sendToPlatform`, `eblPlatform` and `codeListProvider` lists updated with platforms that have been onboarded to the DCSA eBL APIs
- `DOCU` (DocuTrade)
- `AEOT` (AEOTrade)
- `SGTD` (SGTraDex)
- **Transport Document** changes:
- corrected many descriptions for typos and gramatical errors (`numberOfOriginalsWithCharges`, `numberOfOriginalsWithoutCharges`, Reference and ReferenceConsignmentItem `type`, `OuterPackaging`, `packageCode`, `numberOfPackages`, OuterPackaging `description`, `innerPackagings`, `NetExplosiveContent`, NetExplosiveContent `description`, `InnerPackaging`, `UtilizedTransportEquipment`, `VesselVoyage`, `street`, `streetNumber`, `floor`, `postCode`, `city` and `stateRegion`)
- `HSCodes` marked as deprecated everywhere, `extendedHSCodes` to be used instead
- `extendedHSCodes` added in order to support 12 character codes
- `nationalCommodityCodes` marked as deprecated everywhere, `extendedNationalCommodityCodes` to be used instead
- `extendedNationalCommodityCodes` added in order to support 16 character codes
- `innerPackagings` can now have a nested `innerPackagings` to allow multiple innerPackaging-layers
- `role` added to `VesselVoyage` in order to specify the vessel as being: `FIRST_SEA_GOING` (First sea giong vessel) or `MOTHER` (Mother vessel)
- an unstructured address object called `addressLines` added to: `PlaceOfReceipt`, `PlaceOfDelivery` and `OnwardInlandRouting`. Also added to the following party objects: `Shipper`, `OnBehalfOfShipper`, `Consignee`, `OnBehalfOfConsignee`, `Endorsee`, `CarriersAgentAtDestination`, `NotifyParty`, general `Party` and `IssuingParty`
- `facilityName` added to the following location objects: `PlaceOfReceipt`, `PlaceOfDelivery`, `OnwardInlandRouting`
- `chargeName` marked as deprecated - use `extendedChargeName` instead which covers 100 characters (instead of 50 characters)
- `eblPlatform` added to: `Shipper`, `Consignee` and `Endorsee` party objects

<a name="v302"></a>[Release v3.0.2 (14 November 2025)](https://app.swaggerhub.com/apis-docs/dcsaorg/DCSA_EBL_ISS/3.0.2)
---
Expand Down
Loading