Search Results

When should I create a Cloudex API key? Create a Cloudex API key when another system needs to exchange data with your Cloudex TMS account through the Cloudex API. For example, an API integration can be used to: Import shipments/orders into Cloudex TMS fro...

Use this function when your customer uses self-billing — meaning that the customer creates the invoice for your services on your behalf. In Cloudex TMS, you should still create the Outgoing invoice as usual so that the revenue, customer debt and related Clien...

Use the Cloudex TMS API milestones endpoint when an external system needs to update Cloudex TMS about the progress of an existing shipment. Examples include shipment milestone/status updates such as: Shipment loaded; Shipment delivered. Before you star...

Use the Cloudex TMS API documents endpoint when documents from an external system need to be attached to a shipment in Cloudex TMS. Typical examples are: POD (Proof of Delivery); CMR; other shipment-related documents. Before you start The shipment mu...

You can send a transport order directly from Cloudex TMS to your carrier's TMS without sending the order manually by email or entering it again in another system. This option is available when an API integration with the selected carrier's TMS has been config...

Add a carrier's TMS API key when Cloudex TMS needs to send transport orders or other information directly to the carrier's external TMS. For example, if your carrier uses XSPED or Terminality, their API credentials must be registered in Cloudex TMS before you...

Cloudex TMS can automatically request shipment updates and missing documents from the carrier during transport. Instead of manually contacting the carrier to ask whether the cargo has been loaded or delivered, or to request a POD/CMR, Cloudex can send these r...