This is a technical implementation guide to the DCSA electronic Bill of Lading (EBL) standard version 3.0. The audience of this document is technical teams of DCSA adopting organizations.
Calling: POST /shipping-instructions
POST request to create a Shipping Instructions.GET response.202 (Accepted) containing only the shippingInstructionsReference.
RECEIVED)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.202 (Accepted) / 404 (Not Found) / 409 (Conflict) without content.
RECEIVED)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.404 (Not Found) as no update exists.
RECEIVED)Calling: GET /transport-document/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.404 (Not Found) as no Transport Document exists.
RECEIVED.POST /shipping-instructions-notifications)
shippingInstructions property) is included, also containing feedbackINFO feedback in the root but not within the Shipping Instructions, or the other way around).id or previous notification id maybe reused.
RECEIVED)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
Feedbacks property in the Shipping Instructions.GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
RECEIVED)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.404 (Not Found) as no update exists.
RECEIVED)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).404 (Not Found).Back to Table of Content ⬆️
PENDING_UPDATE.POST /shipping-instructions-notifications).
Shipping Instructions property) is included, MUST also contain feedback.INFO feedback in the root but not within the Shipping Instructions, or the other way around).id or previous notification id can be reused.
PENDING_UPDATE)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
PENDING_UPDATE)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.404 (Not Found) as no update exists after the status has changed to PENDING_UPDATE.
PENDING_UPDATE)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).404 (Not Found).Back to Table of Content ⬆️
Calling: PUT /shipping-instructions/{documentReference} 1
PUT request to update Shipping Instructions.GET response.202 (Accepted).
404 (Not Found) is returned if the documentReference 1 is not known.409 (Conflict) is returned if the Carrier is processing a Shipping Instructions request.RECEIVED or PENDING_UPDATE).
RECEIVED)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
PENDING_UPDATE)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
RECEIVED)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.UPDATE_CONFIRMED) then the Carrier responds with a 200(Ok) with the content of the previous accepted Updated Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Update Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Updated Shipping Instructions asynchronously).UPDATE_RECEIVED) then the Carrier responds with 200 (Ok) with the content of the (last) Updated Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Updated Shipping Instructions asynchronously).404 (Not Found) as no update exists.
PENDING_UPDATE)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.404 (Not Found) as no update exists.UPDATE_RECEIVED) then the Carrier responds with 200 (Ok) with the content of the (last) Updated Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Updated Shipping Instructions asynchronously).
RECEIVED or PENDING_UPDATE)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).404 (Not Found).
UPDATE_RECEIVED (the Shipping Instructions state is unchanged).POST /shipping-instructions-notifications).
Shipping Instructions property) is included, also containing feedback (mandatory if Shipping Instructions state is PENDING_UPDATE and optional if the Shipping Instructions state is RECEIVED)Updated Shipping Instructions property) is included, optionally containing feedbackINFO feedback in the root but not within the updated Shipping Instructions, or the other way around).id or previous notification id can be reused.
UPDATE_RECEIVED)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
UPDATE_RECEIVED)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.200 (Ok) with the content of the updated Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the updated Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the updated Shipping Instructions asynchronously).
UPDATE_RECEIVED)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).404 (Not Found).Back to Table of Content ⬆️
RECEIVED.UPDATE_CONFIRMED.POST /shipping-instructions-notifications).
Shipping Instructions property) is included, also containing optional feedback connected to the Shipping InstructionsUpdated Shipping Instructions property) is included, also containing optional feedback connected to the updateINFO feedback in the root but not within the Shipping Instructions, or the other way around).id or previous notification id maybe reused.
RECEIVED)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).👉Important note: The content of the Shipping Instructions and the Updated Shipping Instructions are the same.
UPDATE_CONFIRMED)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.200 (Ok) with the content of the updated Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the updated Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the updated Shipping Instructions asynchronously).👉Important note: The content of the Shipping Instructions and the Updated Shipping Instructions are the same.
RECEIVED and updated Shipping Instructions is in state UPDATE_CONFIRMED)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).404 (Not Found).
RECEIVED or PENDING_UPDATE)UPDATE_DECLINED.POST /shipping-instructions-notifications).
Shipping Instructions property) is included, also containing optional feedback connected to the Shipping Instructions (the feedback is mandatory if the state of the Shipping Instructions is PENDING_UPDATE)Updated Shipping Instructions property) is included, also containing optional feedback connected to the updateINFO feedback in the root but not within the Shipping Instructions, or the other way around).id or previous notification id maybe reused.
RECEIVED or PENDING_UPDATE)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
PENDING_UPDATE the feedback is mandatory).GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
UPDATE_DECLINED)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.200 (Ok) with the content of the updated Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the updated Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the updated Shipping Instructions asynchronously).
RECEIVED or PENDING_UPDATE and updated Shipping Instructions is in state UPDATE_DECLINED)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).404 (Not Found).Back to Table of Content ⬆️
Calling: PATCH /shipping-instructions/{documentReference} 1
with payload:
{
"updatedShippingInstructionsStatus": "UPDATE_CANCELLED"
}
PATCH request to cancel a Shipping Instructions update.202 (Accepted).
404 (Not Found) is returned if the documentReference 1 is not known or no update exists.409 (Conflict) is returned if the Carrier is processing a Shipping Instructions request.RECEIVED or PENDING_UPDATE).UPDATE_RECEIVED).
RECEIVED or PENDING_UPDATE)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
PENDING_UPDATE - the feedback is mandatory)GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
UPDATE_RECEIVED)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.200 (Ok) with the content of the updated Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
RECEIVED or PENDING_UPDATE and updated Shipping Instructions is in state UPDATE_RECEIVED)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).404 (Not Found).
RECEIVED or PENDING_UPDATE).UPDATE_CANCELLED.POST /shipping-instructions-notifications).
shippingInstructions property) is included, also containing optional feedback connected to the Shipping Instructions (if the Shipping Instructions is in state PENDING_UPDATE - the feedback is mandatory)updatedShippingInstructions property) is included, also containing optional feedback connected to the updateINFO feedback in the root but not within the Shipping Instructions, or the other way around).id or previous notification id maybe reused.
RECEIVED or PENDING_UPDATE)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
PENDING_UPDATE - the feedback is mandatory)GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
UPDATE_CANCELLED)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.200 (Ok) with the content of the updated Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
RECEIVED or PENDING_UPDATE and updated Shipping Instructions is in state UPDATE_CANCELLED)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).404 (Not Found).
RECEIVED or PENDING_UPDATE).UPDATE_RECEIVED.POST /shipping-instructions-notifications).
shippingInstructions property) is included, also containing optional feedback connected to the Shipping Instructions (if the Shipping Instructions is in state PENDING_UPDATE - the feedback is mandatory)updatedShippingInstructions property) is included, also containing optional feedback connected to the updateINFO feedback in the root but not within the Shipping Instructions, or the other way around).id or previous notification id maybe reused.
RECEIVED or PENDING_UPDATE)Calling: GET /shipping-instructions/{documentReference} 1
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
PENDING_UPDATE - the feedback is mandatory)GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
UPDATE_RECEIVED)Calling: GET /shipping-instructions/{documentReference}?updatedContent=true 1
GET request with the updatedContent query parameter set to true to retrieve the updated Shipping Instructions.200 (Ok) with the content of the updated Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).
RECEIVED or PENDING_UPDATE and updated Shipping Instructions is in state UPDATE_RECEIVED)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).404 (Not Found).Back to Table of Content ⬆️
DRAFT.POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedback.INFO feedback in the root but not within the Transport Document, or the other way around).id or previous notification id can be reused.
DRAFT)Calling: GET /transport-documents/{transportDocumentReference}
GET request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Transport Document asynchronously).Back to Table of Content ⬆️
Calling: PATCH /transport-documents/{transportDocumentReference}
with payload:
{
"transportDocumentStatus": "APPROVED"
}
PATCH request to approve a Transport Document.202 (Accepted).
404 (Not Found) is returned if the transportDocumentReference is not known.409 (Conflict) is returned if the Carrier is processing a Transport Document request.DRAFT).
DRAFT)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).
APPROVED.POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedbackINFO feedback in the root but not within the approved Transport Document, or the other way around).id or previous notification id can be reused.
APPROVED)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).Back to Table of Content ⬆️
ISSUED.POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedback.INFO feedback in the root but not within the Transport Document, or the other way around).id or previous notification id can be reused.
👉 Important note: If the transportDocumentTypeCode='BOL' then the Transport Document will be issued to an eBL Solution Provider via the Issuance API (using PUT /v3/ebl-issuance-requests).
ISSUED)Calling: GET /transport-documents/{transportDocumentReference}
GET request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Transport Document asynchronously).Back to Table of Content ⬆️
Calling: POST /v3/ebl-surrender-requests (via Surrender API)
with (example) payload:
{
"surrenderRequestReference": "{Surrender Request Reference}",
"transportDocumentReference": "{Transport Document Reference}",
"surrenderRequestCode": "AREQ",
"endorsementChain": [...{The endorsement chain}...]
}
POST request to Surrender a Transport Document for amendment.ISSUED).
ISSUED)Calling: GET /transport-documents/{transportDocumentReference} (via eBL API)
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).
PENDING_SURRENDER_FOR_AMENDMENT.POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedbackINFO feedback in the root but not within the Transport Document, or the other way around).id or previous notification id can be reused.
PENDING_SURRENDER_FOR_AMENDMENT)Calling: GET /transport-documents/{transportDocumentReference} (via eBL API)
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).Back to Table of Content ⬆️
SURRENDERED_FOR_AMENDMENT.POST /v3/ebl-surrender-responses request back to the eBL Solution Provider with the following payload:
{
"surrenderRequestReference": "{Surrender Request Reference}",
"action": "SURR"
}
POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedbackINFO feedback in the root but not within the Transport Document, or the other way around).id or previous notification id can be reused.
SURRENDERED_FOR_AMENDMENT)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).
ISSUED.POST /v3/ebl-surrender-responses request back to the eBL Solution Provider with the following payload:
{
"surrenderRequestReference": "{Surrender Request Reference}",
"action": "SREJ"
}
POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedbackINFO feedback in the root but not within the Transport Document, or the other way around).id or previous notification id can be reused.
ISSUED)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).Back to Table of Content ⬆️
VOIDED.POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedback.INFO feedback in the root but not within the Transport Document, or the other way around).id or previous notification id can be reused.
ISSUED.POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedback.INFO feedback in the root but not within the Transport Document, or the other way around).id or previous notification id can be reused.
👉 Important note: If the transportDocumentReference is being reused for the amended Transport Document - the two Transport Document notifications will contain the same transportDocumentReference - the only way to distinguish the two is via the time property of the Notification (the VOIDED notification should be sent before the ISSUED notification).
👉 Important note: If the transportDocumentReference is being reused then it is not possible to GET the VOIDED (Surrendered) Transport Document once the amended Transport Document has been ISSUED. A GET /transport-documents/{transportDocumentReference} would fetch the new Amended Transport Document. It is only possible to fetch the two different Transport Documents if they have different transportDocumentReference.
Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content (explained above) of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).Back to Table of Content ⬆️
Calling: POST /v3/ebl-surrender-requests (via Surrender API)
with (example) payload:
{
"surrenderRequestReference": "{Surrender Request Reference}",
"transportDocumentReference": "{Transport Document Reference}",
"surrenderRequestCode": "SREQ",
"endorsementChain": [...{The endorsement chain}...]
}
POST request to Surrender a Transport Document for delivery.ISSUED).
ISSUED)Calling: GET /transport-documents/{transportDocumentReference} (via eBL API)
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).
PENDING_SURRENDER_FOR_DELIVERY.POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedbackINFO feedback in the root but not within the Transport Document, or the other way around).id or previous notification id can be reused.
PENDING_SURRENDER_FOR_DELIVERY)Calling: GET /transport-documents/{transportDocumentReference} (via eBL API)
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).Back to Table of Content ⬆️
SURRENDERED_FOR_DELIVERY.POST /v3/ebl-surrender-responses request back to the eBL Solution Provider with the following payload:
{
"surrenderRequestReference": "{Surrender Request Reference}",
"action": "SURR"
}
POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedbackINFO feedback in the root but not within the Transport Document, or the other way around).id or previous notification id can be reused.
SURRENDERED_FOR_DELIVERY)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).
ISSUED.POST /v3/ebl-surrender-responses request back to the eBL Solution Provider with the following payload:
{
"surrenderRequestReference": "{Surrender Request Reference}",
"action": "SREJ"
}
POST /shipping-instructions-notifications).
Transport Document property) is included, also containing feedbackINFO feedback in the root but not within the Transport Document, or the other way around).id or previous notification id can be reused.
ISSUED)Calling: GET /transport-documents/{transportDocumentReference}
GET Transport Document request to retrieve the Transport Document.200 (Ok) with the content of the Transport Document (or a 202 (Accepted) in case the Carrier is in the middle of processing the Transport Document).Back to Table of Content ⬆️
COMPLETED.POST /shipping-instructions-notifications).
Shipping Instructions property) is included, also containing feedback.INFO feedback in the root but not within the Shipping Instructions, or the other way around).id or previous notification id can be reused.
COMPLETED)Calling: GET /shipping-instructions/{shippingInstructionsReference}
GET request to retrieve the Shipping Instructions.200 (Ok) with the content of the Shipping Instructions (or a 202 (Accepted) / 409 (Conflict) in case the Carrier is in the middle of processing the Shipping Instructions).
GET requests MAY return different feedback (e.g. the Carrier MAY still be processing the Shipping Instructions asynchronously).Back to Table of Content ⬆️