From fee05143b15a3cb98481be55c68767a8a9cbe7ad Mon Sep 17 00:00:00 2001 From: "henrik.larsen@dcsa.org" Date: Tue, 27 Jan 2026 09:11:44 +0100 Subject: [PATCH 1/2] EBL 3.0: SD-2793: Update API description --- pint/v3/EBL_PINT_v3.0.0.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pint/v3/EBL_PINT_v3.0.0.yaml b/pint/v3/EBL_PINT_v3.0.0.yaml index 94860568..030c0e16 100644 --- a/pint/v3/EBL_PINT_v3.0.0.yaml +++ b/pint/v3/EBL_PINT_v3.0.0.yaml @@ -21,8 +21,8 @@ info: The PINT API is designed to support transfer of the following types of eBL documents: 1. Straight eBL documents. This type of eBL document is defined by [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `false` - 2. Blank-endorsed eBL documents. This type of eBL document is created by setting [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `true`, and making sure that [`EblEnvelope.transportDocument.documentParties[]`](#/EblEnvelope) list does not contain document party where `DocumentParty.partyFunction` has value `END` (Endorsee) - 3. To-order/Negotiable eBL documents. This type of eBL document is created by setting the [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `true`, and making sure that [`EblEnvelope.transportDocument.documentParties[]`](#/EblEnvelope) list contains document party where `DocumentParty.partyFunction` has value `END` (Endorsee). If the current endorsee party is also in possession of the eBL (possessor), this party can endorse some other party on the same eBL Platform (and make that other party new endorsee) by executing transaction with [`Transaction.actionCode`](#/Transaction) type `ENDORSE` (Endorsement). The DCSA PINT API support To-order/Negotiable documents, however, given that not all of the eBL solution providers support the split between possession and endorsements, this doesn't apply yet to interoperable eBL + 2. Blank-endorsed eBL documents. This type of eBL document is created by setting [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `true`, and making sure that [`EblEnvelope.transportDocument.documentParties`](#/EblEnvelope) object does not contain the `endorsee` document party object + 3. To-order/Negotiable eBL documents. This type of eBL document is created by setting the [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `true`, and making sure that [`EblEnvelope.transportDocument.documentParties`](#/EblEnvelope) object contains the `endorsee` document party object. If the current endorsee party is also in possession of the eBL (possessor), this party can endorse some other party on the same eBL Platform (and make that other party new endorsee) by executing transaction with [`Transaction.actionCode`](#/Transaction) type `ENDORSE` (Endorsement). The DCSA PINT API support To-order/Negotiable documents, however, given that not all of the eBL solution providers support the split between possession and endorsements, this doesn't apply yet to interoperable eBL

The Additional Documents

From 8022fe925a68097fe100f75641ba141d1fd2113e Mon Sep 17 00:00:00 2001 From: "henrik.larsen@dcsa.org" Date: Tue, 27 Jan 2026 14:44:31 +0100 Subject: [PATCH 2/2] Improve "To order/Negotiable eBL documents" description --- pint/v3/EBL_PINT_v3.0.0.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pint/v3/EBL_PINT_v3.0.0.yaml b/pint/v3/EBL_PINT_v3.0.0.yaml index 030c0e16..92f59883 100644 --- a/pint/v3/EBL_PINT_v3.0.0.yaml +++ b/pint/v3/EBL_PINT_v3.0.0.yaml @@ -20,9 +20,9 @@ info: The envelope transfer from the sending eBL Platform to the receiving eBL Platform always contains the **eBL document** (transferred via [**'Start envelope transfer'**](#/Start%20envelope%20transfer) endpoint request body [`EblEnvelope.transportDocument`](#/EblEnvelope) schema object). The eBL document must be unchanged between different envelope transfers for the lifetime of the eBL document. The PINT API is designed to support transfer of the following types of eBL documents: - 1. Straight eBL documents. This type of eBL document is defined by [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `false` - 2. Blank-endorsed eBL documents. This type of eBL document is created by setting [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `true`, and making sure that [`EblEnvelope.transportDocument.documentParties`](#/EblEnvelope) object does not contain the `endorsee` document party object - 3. To-order/Negotiable eBL documents. This type of eBL document is created by setting the [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `true`, and making sure that [`EblEnvelope.transportDocument.documentParties`](#/EblEnvelope) object contains the `endorsee` document party object. If the current endorsee party is also in possession of the eBL (possessor), this party can endorse some other party on the same eBL Platform (and make that other party new endorsee) by executing transaction with [`Transaction.actionCode`](#/Transaction) type `ENDORSE` (Endorsement). The DCSA PINT API support To-order/Negotiable documents, however, given that not all of the eBL solution providers support the split between possession and endorsements, this doesn't apply yet to interoperable eBL + 1. Straight eBL documents. This type of eBL document is defined by [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `false`. + 2. Blank-endorsed eBL documents. This type of eBL document is created by setting [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `true`, and making sure that [`EblEnvelope.transportDocument.documentParties`](#/EblEnvelope) object does **not** contain an `endorsee` document party. + 3. To-order/Negotiable eBL documents. This type of eBL document is created by setting the [`EblEnvelope.transportDocument.isToOrder`](#/EblEnvelope) attribute to `true` and ensuring that the [`EblEnvelope.transportDocument.documentParties`](#/EblEnvelope) object contains an `endorsee` document party. If the current endorsee is also in possession of the eBL (i.e. is the possessor), that party may endorse the EBL to another party - either on the same eBL Platform or on a different eBL Platform - thereby making that other party the new endorsee. This is done by executing a transaction with [`Transaction.actionCode`](#/Transaction) set to `ENDORSE`, `ENDORSE_TO_ORDER` or `BLANK_ENDORSE`. The DCSA PINT API support To-order/Negotiable documents accross platforms; however, it is the responsibility of each eBL Solution Provider to validate whether the receiving platform supports such documents.

The Additional Documents