Issuer Exchange API handles all relevant operations required by Line/NVOCC Customers/Future Warehouse. Some endpoints are regularly used whereas a couple of the endpoints are needed to be executed as required. Several Action endpoints use can use to Action over a transaction (or more specifically the eBoL/eWW/etc. in a set of documents). Due to the value of these documents (eBoLs, etc.), and to avoid cross-platform liabilities, essDOCS employs a Verified by CargoDocs step, which requires the user to confirm any step before it is actioned.
This API allows the carriers to match their consignee names to Consignees signed up to transfer eBoLs in CargoDocs. Note that this API is not required if the eBoL is a Bearer eBoL and the eBoL is issued to the shipper.
This API allows issuers to find specific transactions or all transactions for a customer that they are authorized to download / manage. It always returns a list of set DTOs, which includes set_id & transaction_id; and set meta data If search result is unique, then will return document XML data and document_ids along with DTO.
This is a Set Action endpoint that is used for different actions through out the API for different purposes. This endpoint has a relevant request body to convert Bol to next stage if assigned to Destination Team already.