Skip to main content

CargoDocs APIs & Data Interfacing 

Interfacing to CargoDocs allows users to access the solution via a B2B method, rather than requiring them to login to the solution. This approach provides for maximum flexibility, in addition to increased accessibility and ease of use.

Users can do the following through an interface:

  • Upload data to generate shipping documentation, for example Bills Of Lading, Certificates, Inspection Reports, Timesheets etc.
  • Download business transaction and status information relating to active or historic shipments
  • Download the data relating to shipment document sets, i.e., eB/L plus supporting document data, in XML format
  • Download shipment document sets, i.e., eB/L plus supporting documents, in PDF
  • Via DocEx Open API:
    • Integrate Data/PDFs, enabling seamless connectivity and transfer between systems & solutions
    • Functionally integrate, providing a seamless User Experience within a customer or partner solution, avoiding the need to login to DocEx at any point to manage CargoDocs actions such as signing, issuing, transferring or presenting original eDocs

Interfaces for Tankers:

  • Web service interface – essDOCS has already developed interfaces with a number of common hydrocarbon accounting / terminal operational systems, including:
    • Maron Systems: Oil Accounting and Shipping (OAS)
    • Implico: OpenTAS module for SAP
    • Tieto: Energy Components (EC)

Interfaces for Bulker:

  • Web service interface
  • Via GlobalShare edoxOnline
  • CargoDocs DocHub SAP Interface

Interfaces for Barges:

Terminals and Refineries tend to interface directly with CargoDocs to receive Load and Discharge nominations as data, as well as push Sailing Advice and/or eBarge Documents to the exchange. Current interfaces for Barges include:

  • Standard Java API
  • Web Service Interface

Interface for Liner:

  • EDI upload interface

Interfaces for Trade Finance:

  • Web Interface
  • Via SWIFT
  • Via R3 Voltron
  • Via another multi-bank platform (i.e., eLCY, GlobalTrade Corp, etc.)
  • Via your proprietary solution (nb., this requires a single-sign-on implementation)